The other issue that has bitten me numerous times is a kernel stack overflow when using xfs and NFS together which results in system lock up. On a given production system it occurs every 2 to 4 weeks - enough to be embarassing. There was a developers thread discussing this a while back but I have not heard of any fixes subsequently. This is the one issue that makes me cautious about using xfs in future. Can anyone bring me up to date?
Posted Jan 21, 2012 20:02 UTC (Sat) by dmcguicken (guest, #57851)
[Link]
!
Do you have any other details on this? I have a sneaking suspicion this is EXACTLY what I was seeing on a little VIA box of mine that I blamed on a faulty I/O daughterboard.
I was using a 1/2 TB external USB drive with XFS for my MythTV recordings, shared over the LAN via NFSv4... and I saw hard lockups every few weeks, pretty reliably.
XFS: the filesystem of the future?
Posted Jan 23, 2012 10:21 UTC (Mon) by flashydave (subscriber, #29267)
[Link]
Posted Jan 22, 2012 12:04 UTC (Sun) by dgc (subscriber, #6611)
[Link]
Hi Flashydave,
If you don't report problems like this to the developers, then we don't know you are having them. The reason the stack overflow fix has not been pushed is that it might have unexpected performance issues due to moving allocation work into workqueues where they have a full stack to work with. Seeing that there has only be a couple of reports of stack overflows on the list in the past 2 years, it doesn't appear to be a widely occurring problem. Hence the urgency for the fix does not appear to be that great and so fixing it can wait until we fully understand the implications of the proposed fix.
IOWs, the frequency or likelihood of occurence of a problem greatly influences decisions on whether to push fixes right now or wait for more testing. So, don't assume that we know how much your systems are affected by the problem even thought we might discussing a possible fix - report them xfs@oss.sgi.com so we are guaranteed to know about them and can take that into account.
As it is, I have been testing the fix for some time now so I'm now pretty confident it doesn't cause any regressions. I'm definitely considering re-prosing it again for the next merge cycle now that I have a lot more testing done on it...
Dave.
XFS: the filesystem of the future?
Posted Jan 23, 2012 10:19 UTC (Mon) by flashydave (subscriber, #29267)
[Link]
Sorry - I was under the impression from the threads I was reading it was a well documented issue and that it was not particularly helpful to simply say "me too".
XFS: the filesystem of the future?
Posted Jan 30, 2012 0:11 UTC (Mon) by sbergman27 (guest, #10767)
[Link]
"""
I was under the impression from the threads I was reading it was a well documented issue and that it was not particularly helpful to simply say "me too".
"""
Nevertheless, it was negligent of you not to jump through all the required hoops to register your bug report. Just because a hundred people before you had already reported it does *not* mean that the devs would necessarily have noted the problem then, or admit to it existing now. Your data loss was your fault. Because you did not bother to file a bug.
FS developers toil day and night, and the only payment they get is fame, glory, and money. Any data loss is the fault of the user.
XFS: the filesystem of the future?
Posted Jan 30, 2012 10:59 UTC (Mon) by nix (subscriber, #2304)
[Link]
FS developers toil day and night, and the only payment they get is fame, glory, and money.
What world do you live in, and how can I move there?
XFS: the filesystem of the future?
Posted Feb 6, 2012 3:16 UTC (Mon) by chip (subscriber, #8258)
[Link]
I gave up on XFS when it started leaving me files of NULs after crashes. I understand they fixed that problem, but until iops are my limiting factor why should I leave ext4?
XFS: the filesystem of the future?
Posted Feb 7, 2012 16:26 UTC (Tue) by phoenix (guest, #73532)
[Link]
Which version of the kernel, XFS, and NFS?
We use XFS and NFS on ~50 servers, serving 1-2 TB of RAID/LVM to 100-400 diskless stations each, without running into any kernel stack overflows or other lockups.
64-bit Debian 5.0.
If this is something new (since kernel 2.6.32), we'd like to know. :)