public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Chris Samuel <csamuel@vpac.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem shutting down on linux 2.6.28.10 (xfs_rename)
Date: Tue, 04 Aug 2009 23:26:49 -0500	[thread overview]
Message-ID: <4A790A09.8050502@sandeen.net> (raw)
In-Reply-To: <1367391532.793061249444829356.JavaMail.root@mail.vpac.org>

Chris Samuel wrote:
> Hi folks,
> 
> I believe we've been hitting the same issue that
> Gabriel Barazer reported in 2.6.28.9 on the 22nd
> of July on our NFS server for our HPC Linux clusters.

...

> This kernel is built with XFS as a kernel module so I've
> been able to attach the objdump output that Eric Sandeen
> had originally requested from Gabriel.

I'll take a look.  The reason for the objdump was to try to work out
where in xfs_rename we were erroring out, but in your case:

xfs_rename+0x5ac/0x5af

I guess it's the trans_cancel at the very end of the function on the
goto <blah>: error cases.

Is there any chance you could instrument xfs_rename so that for every
goto abort_return and goto error_return you add a printk so we know
which one you hit?

Maybe something like:

printk("line %s error %d\n", __LINE__, error);

just before each goto, with appropriate braces {} sprinkled in as necessary?

I can send a patch if that helps.

Sorry for the brute-force debugging but not at all sure yet what this
may be.

Thanks,
-Eric

> Like Gabriel we're stuck on 2.6.28.x as the last working
> NFS exporting XFS kernel due to kernel bug #13375 (the
> radix bug), so I hope this helps!
> 
> cheers,
> Chris
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-05  4:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <816101050.793011249444717925.JavaMail.root@mail.vpac.org>
2009-08-05  4:00 ` XFS filesystem shutting down on linux 2.6.28.10 (xfs_rename) Chris Samuel
2009-08-05  4:26   ` Eric Sandeen [this message]
2009-08-05  4:32     ` Chris Samuel
2009-08-10  8:20   ` Krzysztof Błaszkowski
2009-08-10 14:29   ` Eric Sandeen
2009-08-10 22:52     ` Chris Samuel
2009-08-10 23:20       ` Eric Sandeen
     [not found] <1055011478.793231249445110983.JavaMail.root@mail.vpac.org>
2009-08-05  4:05 ` Chris Samuel
     [not found] <7684694.1055541249875694469.JavaMail.root@mail.vpac.org>
2009-08-10  3:43 ` Chris Samuel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A790A09.8050502@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=csamuel@vpac.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox