public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alex Samad <alex@samad.com.au>
Cc: randrik@mail.ru, xfs@oss.sgi.com
Subject: Re: Kernel crash with 2.6.29 + nfs + xfs (radix-tree)
Date: Tue, 26 May 2009 05:09:16 -0400	[thread overview]
Message-ID: <20090526090916.GA17194@infradead.org> (raw)
In-Reply-To: <20090520095639.GA27496@samad.com.au>

So you're having primary a NFS workload, right?  Andrew had some
dmesg output in bugzilla (please send this stuff to the list instead
of hiding it in bugzilla if possible, BTW) that looks quite interesting:

May 24 08:48:00 (none) last message repeated 61 times                           
May 24 08:48:47 (none) last message repeated 760 times                          
May 24 08:50:55 (none) kernel: reconnect_path: npd != pd                        
May 24 08:50:55 (none) last message repeated 9 times                            
May 24 08:55:04 (none) kernel: reconnect_path: npd != pd                        
May 24 08:56:05 (none) last message repeated 47 times                           
May 24 08:56:49 (none) last message repeated 419 times

which means we are in deep trouble with the dcache coherency.  Also
the only way the bug you two report could happen from my audit is
we get ->destroy_inode called twice for the same inode.

So defintively some deep problems here.  Alex and Andrew, can you send
me your .config, and a description of the workload your seing this on?
Also the /etc/exports file would be interesting.

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

  reply	other threads:[~2009-05-26  9:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090520003745.GA27491@samad.com.au>
2009-05-20  9:05 ` Kernel crash with 2.6.29 + nfs + xfs (radix-tree) Dave Chinner
2009-05-20  9:56   ` Alex Samad
2009-05-26  9:09     ` Christoph Hellwig [this message]
2009-05-27  2:54       ` Alex Samad
2009-06-04 11:26         ` Christoph Hellwig
2009-06-05 11:20           ` Martin Spott
2009-06-07 17:28           ` Martin Spott
2009-06-07 18:27             ` Felix Blyakher
2009-06-07 18:27             ` Eric Sandeen
2009-06-07 18:55               ` Martin Spott
2009-06-07 18:55             ` Christoph Hellwig
2009-06-07 20:00               ` Martin Spott
2009-06-07 20:44                 ` Christoph Hellwig
2009-06-07 21:26                   ` Martin Spott
2009-06-08 20:13                     ` Martin Spott
2009-06-09  8:40                       ` Christoph Hellwig
2009-05-27 17:21       ` Martin Spott
2009-05-27 18:05         ` Martin Spott

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=20090526090916.GA17194@infradead.org \
    --to=hch@infradead.org \
    --cc=alex@samad.com.au \
    --cc=randrik@mail.ru \
    --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