On 05/03/2015 10:46 AM, David C. Rankin wrote:
I have never, in the 17 years I've worked with Linux, seen so many FS failures with data loss as I've seen in the past 12 months related to btrfs.
While some parts of your post may have been over the top, (just a tad), by and large this is spot on. Look to my left, I see a very heavily uses Windows 7 (upgraded from Vista) 7 or 9 years old, and I've never had a bit of file system problems in-spite of it running almost 24/7 over those years. I have an old Opensuse file server, much older running Reiserfs on mdRaid, probably 12 years old and had problems exactly once when a disk failed. _No data loss._ No need to restore from backup. Yet my main Linux machine had two BTRFS crashed, necessitating FS rebuilds, one with massive data loss, requiring re-installation. (yes it was backed up). _All within 6 months_. (I didn't have my work source code library nor my /home directory on BTRFS, thank my lucky stars.) Additionally, opensuse decided to never purge ANY temp files, and save ridiculous amounts BTRFS snapsots, and put /tmp and /var/tmp on BTRFS as sub-volumes putting the whole installation at risk of a full /tmp, on an experimental file system. /Root would have been fine on btrfs, because you should be able to install anything on there again if it goes bad (other than /etc). But /tmp and /var/tmp are very active and dynamic. Side Issue --------- (or maybe the root problem?) As best I understand the situation, MicroFocus (yes the PC COBOL company) now owns Suse Linux. Therefore Opensuse is no longer a testbed for SLED/SLES. Its time for Opensuse to stop serving as the crash-test-dummy distro. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org