jwmitchell wrote:We recommending using a subvolume for root and our new UEK ISO automatically creates a subvolume for root during the install process. We don't however create the more complex layout that Arch does for example.
But are there any Oracle recommendations? When the UEK2/btrfs IOS is released, how will it build the btrfs filesystem? From those who may have experience with btfs, what are your thoughts?
Sorry to interfere, I hope it's ok. I noticed that one actually does not need an explicit subvolume to create a snapshot:
What is the advantage of having root in an explicit subvolume?Means you can do snapshot comparisons against the subvolume at any time, i.e. if your active / partition is a subvolume, and you snapshot it, you can see both in the snapshot/subvolume list and compare them. You can also snapshot the previous snapshot or revert back, etc.
Is there a particular name recommended, such as "__active", like the OP outlined?Not really. You can chose whatever works for your own sysadmin style. Ubuntu uses a different naming convention to Arch, for example.
Dude wrote:Yes, but I've seen similar guidance in forums from a variety of distros.
Are you referring to: https://wiki.archlinux.org/index.php/Installing_on_Btrfs_root ?
Regarding your other thread about btrfs... I'm currently doing some more testing and will do some update on my howto. I did not reply further because I did not have any luck starting from a system were /var is a btrfs subvolume. Perhaps there is something wrong with the driver or there is some other boot parameter or trick required.Thanks for continuing to look at this. I'm interested in what you find. However I've decided making /var a subvolume isn't such a great idea after all. I originally thought btrfs subvolumes worked similar to their ZFS counterparts, in other words, a snapshot of the / filesystem would propogate down through the various subvolumes. But after reading through the documents on https://btrfs.wiki.kernel.org discovered that isn't the case. This would seem to limit the value of btrfs subvolumes since I can't get a point-in-time snapshot of the entire filesystem.