OTOH, LVM must copy the block to every snapshot before it can change it in the parent. When the parent data for a ZFS snapshot changes, ZFS merely has to leave the old data alone. Say I want to take hourly snapshots, and retain them for a month. All that without tying you to a single file system (though that may be a moot point on OS X, as it will only boot from HFS/HFS+ AFAIK). Those systems provide RO and RW snapshots, dynamic partitioning, drive spanning, etc., and can be easily layered with other block-level components to provide compression, encryption, remote storage, etc. I'd much rather have volume or block level snapshots, like with LVM and other similar systems. They might be new OS X, or repackaged in a way that's easy to consume, but they are things that anyone with big disks has been doing for years. I'm not saying the features ZFS has are useless - I think they are great - they just aren't all that new and exciting. The only thing you miss here that ZFS may be able to do (I didn't check) is avoid closing the files that are moved.
#Os x server hardware update#
If you really wanted to you could even write a script that takes no arguments other than a path name and automatically created a series of volumes of an appropriate size for the folder you selected, setup software raid to mirror them into a single device, mount the device with a compression filter, format it (with any file system) mount it normally, move the data over, drop the old data, rebind the mount point to the old path name, and update fstab.
What is it with you people and filesystem-level snapshots?
#Os x server hardware code#
It already does that, so non-zone ZFS root will NOT require any modifications or upgrades to OpenBoot, just updates to the bootloader code that is written to the disk in blocks 1-8. OpenBoot only needs to understand the disk label/partitioning and to be able to read the disk blocks. OpenBoot loads the next stage of boot code by reading raw data from blocks 1-8 of the chosen slice of the boot disk, and THAT is the code that needs to be able understand the filesystem that will be mounted as root (UFS, ZFS, or whatever). You CAN put a zone root on ZFS at the moment, but Sun neither recommends nor supports that setup.įor SPARC machines, it'll require new OpenBoot firmware that understands zfs.Īnd this is simply untrue, period, even for non-zone ZFS root filesystems.
It's easier.Īctually, GP was talking about ZONE root filesystems, which have absolutely nothing to do with the bootloader, since the zone runs on top of the underlying global zone. This will come first in Solaris 10 x86 because they already have grub there. For that to work, you need a boot loader that supports zfs.
0 kommentar(er)
