Originally posted by starshipeleven
View Post
1. Autodefrag have issues too...
Here you go: https://wiki.debian.org/Btrfs
Look under recommendations for rotational harddisks.... you will find the following....
"Consider revoking this recommendation, because autodefrag, like -o discard, can trigger buggy behaviour. Also consider revoking the compress=lzo recommendation for rotational disks, because while it increases throughput for sequentially written compressible data, it also magnifies fragmentation...which means lots more seeks and increased latency -- NicholasDSteeves"
2. Mailing list post where Chris Murphy says that BTRFS does not have a concept of failed drives...
Here you go: http://www.spinics.net/lists/linux-btrfs/msg57999.html
...and in all fairness - they are working on it... : http://www.spinics.net/lists/linux-btrfs/msg56741.html
3. Mailing list post where a guy is struggling booting with systemd where one disk have gone bad...
Well, this is embarrassing isn't it... I am not able to find that post so I can't back up this one with any evidence. If you *really* want it I can try to look harder.
I can't remember the exact details in that post , but this may absolutely have more to do with the glue around btrfs than btrfs itself.
Leave a comment: