From: Christoph Hellwig <hch@infradead.org>
To: Peter Niemayer <niemayer@isg.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: linux-2.6.34 xfs crash: xfs_inode_ag_iterator+0x6c - NULL pointer dereference
Date: Fri, 11 Jun 2010 12:19:22 -0400 [thread overview]
Message-ID: <20100611161922.GB7556@infradead.org> (raw)
In-Reply-To: <hur8at$jua$1@dough.gmane.org>
On Thu, Jun 10, 2010 at 07:45:01PM +0200, Peter Niemayer wrote:
> Hi,
>
> FYI: attached screen-shot is from a server that crashed today when
> doing an "umount" of a no longer needed XFS partition on a SSD
> (mount options: rw,noatime,nodiratime,nobarrier)
>
> (The operations on that filesystem ended > 1 day before the umount,
> and did not show any problem)
>
> Kernel was plain vanilla 2.6.34.
Unfortunately the backtrace doesn't really tell what has happened as
the origin of the backtrace scrolled away.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-11 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:45 linux-2.6.34 xfs crash: xfs_inode_ag_iterator+0x6c - NULL pointer dereference Peter Niemayer
2010-06-11 16:19 ` Christoph Hellwig [this message]
2010-06-11 16:49 ` Peter Niemayer
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=20100611161922.GB7556@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=niemayer@isg.de \
/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