thin handling of available space
A message that is not in the archive (sent off-list or not yet received): 799090122.6079306.1462373733693.JavaMail.yahoo.ref@mail.yahoo.com
Quoted 2 lines · Mark Mielke
I get a bit lost here in the push towards BTRFS and ZFS for people with these expectations as I see BTRFS and ZFS as having a similar problem. They can both still fill up.
Well of course everything fills up eventually. BTRFS and ZFS are integrated systems where the FS can see into the block layer and "do" block layer activities vs the clear demarcation between XFS/EXT and LVM/MD.
If you write too much to a Thin FS today you get serious data loss. Oh sure, the metadata might have landed but the file contents sure didn't. Somebody (you?) mentioned how you seemingly were able to write 4x90GB to a 300GB block device and the FS fsck'd successfully. This doesn't happen in BTRFS/ZFS and friends. At 300.001GB you would have gotten a write error and the write operation would not have succeeded.