public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Patrick Schreurs <patrick@news-service.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2.6.30 panic - xfs_fs_destroy_inode
Date: Wed, 17 Jun 2009 16:31:12 -0500	[thread overview]
Message-ID: <4A3960A0.8090707@sandeen.net> (raw)
In-Reply-To: <4A392213.4020200@news-service.com>

Patrick Schreurs wrote:
> Hi all,
> 
> We are experiencing kernel panics on servers running 2.6.29(.1) and 
> 2.6.30. I've included two attachments to demonstrate.
> 
> The error is:
> Kernel panic - not syncing: xfs_fs_destroy_inode: cannot reclaim ...
> 
> OS is 64bit Debian lenny.
> 
> Is this a known issue? Any comments on this?

It's not known to me, was this a recent upgrade?  (IOW, did it start
with .29(.1)?

-Eric

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

  reply	other threads:[~2009-06-17 21:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 17:04 2.6.30 panic - xfs_fs_destroy_inode Patrick Schreurs
2009-06-17 21:31 ` Eric Sandeen [this message]
2009-06-18  7:55   ` Patrick Schreurs
2009-06-20 10:18     ` Patrick Schreurs
2009-06-20 13:29       ` Eric Sandeen
2009-06-20 16:31         ` Patrick Schreurs
2009-06-23  7:24           ` Patrick Schreurs
2009-06-23  8:17             ` Lachlan McIlroy
2009-06-23 17:13               ` Christoph Hellwig
2009-06-30 20:13                 ` Patrick Schreurs
2009-06-30 20:42                   ` Christoph Hellwig
2009-07-20 19:19                     ` Patrick Schreurs
2009-07-20 20:14                       ` Christoph Hellwig
2009-07-01 12:44                   ` Christoph Hellwig
2009-07-02  7:09                     ` Tommy van Leeuwen
2009-07-02 17:31                     ` Patrick Schreurs
2009-07-21 14:12                       ` Christoph Hellwig
2009-07-22  8:55                         ` Tommy van Leeuwen
2009-08-17 21:14                           ` Christoph Hellwig
2009-08-20 12:24                             ` Tommy van Leeuwen

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=4A3960A0.8090707@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=linux-xfs@oss.sgi.com \
    --cc=patrick@news-service.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