Once upon a time, Ben Cotton <bcotton@xxxxxxxxxx> said: > For laptop and workstation installs of Fedora, we want to provide file > system features to users in a transparent fashion. We want to add new > features, while reducing the amount of expertise needed to deal with > situations like [https://pagure.io/fedora-workstation/issue/152 > running out of disk space.] Btrfs is well adapted to this role by > design philosophy, let's make it the default. So... I freely admit I have not looked closely at btrfs in some time, so I could be out of date (and my apologies if so). One issue that I have seen mentioned as an issue within the last week is still the problem of running out of space when it still looks like there's space free. I didn't read the responses, so not sure of the resolution, but I remember that being a "thing" with btrfs. Is that still the case? What are the causes, and if so, how can we keep from getting a lot of the same question on mailing lists/forums/etc.? I'm pretty neutral on this... I run a bunch of RHEL/CentOS systems, so I tend to stick close to that on my Fedora systems (so I'd probably stick with ext4/xfs on LVM myself). I remember when btrfs was going to be the one FS to rule them all, but then had issues, and specific weird cases (like with VM images IIRC at one point), and kind of fell of my map then. That is not intended as a criticism - filesystems are complex, and developing them hard... I think some of the reputation came from some people pushing btrfs before it was really ready. -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
