> When you see a oops on any linux box you should always save
> it, decode
> it with ksymoops and send it to one of the development lists (in this
> case to linux-xfs). If you don't do that you should not be
> surprised that
> bugs don't get fixed and you can only blame yourself.
Been there, done that. Spent many an anxious evening saving oops
outputs, running them through ksymoops and adding trying to make sense of it
all - I had plenty to choose from, and I shared them. A quick search finds:
That last post evoked no responses and was pretty much the point
when we decided to bail. To be fair, one of the earlier ones was an oops
which resulted from a conflict between NFS and xfsdump (which I think was
resolved later - we just switched amanda to use tar).
There is no need to be defensive - I am not attacking XFS or saying
it is garbage, etc. Our experience with XFS was a bad one, others not.
Maybe we have some bizarre configuration, maybe we are doing it wrong. But
we arrived at a point where the server was going down every week and we
couldn't get a similar system in a controlled environment to fail, which was
derailing any attempts to debug the problem - it's hard to spent time
figuring out what is going wrong or testing patches with 100+ people waiting
for the NFS server to come back up.
Anyways, if every post was about how wonderful XFS was, what fun
would that be?