On 2018-10-06 7:11 a.m., Dave Howorth wrote:
I'm a bit stuck now; my XFS foo is not strong today, it seems. Can anybody suggest what my next steps should be? I'll keep googling but I hope somebody may have more informed ideas :)
This may or may not be relevant. In my 14.2days I moved to XFS for one FS and had a similar-but-different glitch and fsck didn't help. Carlos suggested that I update the XFS tools. The updated fsck worked. In the long run I switched from XFS to JFS. I've had no problems with JFS. Why would I use wither? The same reason I used ReiserFS - I HATE pre-provisioning. A late model b-tree file system shouldn't need to pre-allocate a fixed number of inodes and a fixed amount of data space. That ideology dates back to the old, old UNIX V6 -- no wait, further back than that in other operating systems. More modern designs, XFS, ReiserFS, JFS and yes, even BtrFS do proper dynamic allocation. You don't get 'out of space' messages when you have plenty of space because the inodes are exhausted. BTDT and I now I'm not alone, I see many questions about this on the net. That ext4 suffers from this pre-provisioning problem as well even though it does manage its structures using b-trees is a design deficiency. My main down with XFS is that it appears, to me, to be too complex. I look at the number of parameters you can play around with, be it at mkfs or later, and compare with ReiserFS, JFS, and, shock-horror, BtrFS and even Ext4. The decision three to 'optimise' for a specific situation is just too much; this is not a 'general purpose' file system. https://linux.die.net/man/8/mkfs.xfs The older I get the more I value KISS. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org