On 11/26/2014 09:06 PM, Neil Rickert wrote:
grub2, and "/boot" in an "ext{2,3,4}" partition: should be okay.
There's a moral her, as I see it. Its the 'just because you can doesn't mean you should' sort of thing. Just because you can put /boot on the BtrFS-all-as-one-file-system ... Having a separate /boot on a simple, well established Fs such as ext2 or ext3 is about 'resilience'. We found that was a way of getting round 'teething' and other unexpected problems with other file systems as that were "in development" and with LVM in its time. I have BtrFS as my ROOT. So far it hasn't given me any problems. But, as regular readers know, I run LVM, and I have another partition I can use as ROOT if BtrFS fails. Yes, there has been discussion of using snapshots as backups (!) but if the file system itself has failed then the snapshots are not going to be accessible. There are many failure modes; taking images with LVM is one of them. These are real images not COWS. Taking proper off-machine backups is another. Restoring from backup can take longer than rebooting using another partition as ROOT. I've never had to reverse a COW snapshot with Linux/BtrFS. I have done it with AIX and IBM supplied all the proper tools to make reversing out of updates & manual changes very straightforward. I'll be glad when we see similar tools -- a sort of "zypper undo using snapshot 'last'". Until then snapshots/COW are in the "nice to have but what am I going to actually _DO_ with them?" category. Snapshots are COW, they are not backup. They are for reversing recent changes, for an arbitrary value of 'recent'. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org