?I have had a bad experience with btrfs and SLES 12.3: - the virtual machine we'd put a lot of work into, wouldn't boot after expanding a btrfs, and had to be recreated along with the work involved. Thankfully, it wasn't me that had to do the work, and Per Rosengren has since filled me in on the steps that are necessary when expanding a btrfs file system. But I am still wondering why I shouldn't go back to using LVM or even a dedicated minidisk for booting, and maybe having other file systems (besides /, /var and /usr ) on btrfs. I've gone through everything I can find on the mailing list, and looked at the btrfs, and I can't find any convincing reasons for using it, except that it seems to be the standard on SLES12.
For me it looks like it fixes something that ain't broke -and, like systemd, makes us learn a bunch of new commands that work differently than the ones we use on other file systems and platforms. Specifically "df" doesn't tell us anything. Putting everything on one btrfs, means that if one of the disks goes bad, everything is trashed. And if something fills up one of the subvolumes, you can't even log in, since all the other volumes - like / and /var, will also be full. How can you put mission critical systems on it? Is anybody else having problems with this? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
