An alternative to serving via HTTP might be to offer some sort of ability to use supplementary media, like a USB stick, to load the binaries but you've still got to compile those binaries to match every installer version you want to support (and add those media hooks to all the relevant installers). That's a fairly significant (and ongoing) task, particularly when installation media may get point releases that require new bins.
If you have the memory, using a livecd should already give you a moderately simple path to doing an initial install onto ZFS, since you should be able to boot to the live environment, install the packages as normal, prepare the disks as ZFS and perform the install onto them, then chroot into the install and perform any final configuration (here's a link for HOWTO install Ubuntu on ZFS root, haven't read it in a while, but from memory that was the gist of it).
thanks a lot ryao !
that's a more in-depth answer than I had anticipated
I'm currently trying out ZFS/ZOL with lz4-algorithm on one of my backup disks and it looks good
I see one issue which hinders me from using lz4 on my laptop / on the root partition: there's no liveCDs with ZOL available that support the LZ4 algorithm
in case things go wrong I would have no access to my data at all if all partitions were using the LZ4 compression algorithm - am I correct ?
not exactly sure what's going on here:
I created the pool with sub-pools/volumes and copied already some data to it (around 800 GB), exported it
booted into windows
now came back to linux and wanted to import it:
zpool import WD30EFRX
cannot import 'WD30EFRX': one or more devices is currently unavailable
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
WD30EFRX FAULTED corrupted data
WDred_zfs UNAVAIL corrupted data
these are pools with compress=lz4 set
I reproducibly got the same error when creating a new pool and after exporting trying to re-import it
any ideas ?
this is on an GPT partition table -> partition
might that be the reason ?
the same happens when using lzjb
Last edited by kernelOfTruth; 04-20-2013 at 11:25 PM.
ryao, you by chance know if suspend-to-ram, so freezing of the filesystem's contents, work with ZFS (I doubt it - but it would be a pleasant surprise)
Those of you who say that ZFS is closed source: it is not. ZFS have been forked, and the Oracle ZFS is closed source, yes. The Illumos (Solaris kernel) have forked ZFS and it is completely open sourced under CDDL. Several OSes use ZFS today: FreeBSD, Mac OS X (Z-410), OpenSolaris, etc.
Both of the head architects of ZFS have quit Sun and one of the them have joined Joyent who also created nodejs. All DTrace creators have joined Joyent too. They work on Illumos, and Joyent has the strongest Solaris kernel hackers outside Oracle. Illumos have several new ZFS functions that even Oracle Solaris does not have. Some believe that Illumos ZFS will surpass Oracle Solaris. Also, a FreeBSD hacker have coded up LZ4 compression algorithm, which is very clever. So, there is lot of momentum in open source ZFS outside Oracle Solaris.
BTW, the well known compression algorithm lzjb (lzJB) is named after Jeff Bonwick, the other head architect of ZFS. Matt Ahrens at Joyent is the other.
But it still open source under CDDL, and several OSes use it. FreeBSD can use it, why can not Linux use it? Mac OS X use it. All OpenSolaris distros use it. Also, Linux use it. Here are all OSes that use it, it is quite a list.