From: Christoph Hellwig <hch@infradead.org>
To: Christopher Layne <clayne@anodized.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_trans_log_inode: OOPS in 2.6.28.7
Date: Mon, 6 Apr 2009 13:40:31 -0400 [thread overview]
Message-ID: <20090406174030.GA8943@infradead.org> (raw)
In-Reply-To: <20090402024744.GB23044@ns1.signalpunk.com>
On Thu, Apr 02, 2009 at 02:47:44AM +0000, Christopher Layne wrote:
> While I think I might be able to reproduce this it's not something I
> particularly want to reproduce. The precursor was cancelling an
> already running xfs_fsr, removing the .fsr_last, and immediately
> restarting it (forcing a new cycle). Right after I received an OOPS and
> all file system access was blocked necessitating a hard reboot and
> xfs_repair.
The a5a5a5 in there looks like slab poisoning. I'll try to come up with
a testcase based on your above report to try to reproduce it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-04-06 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 2:47 xfs_trans_log_inode: OOPS in 2.6.28.7 Christopher Layne
2009-04-06 17:40 ` Christoph Hellwig [this message]
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=20090406174030.GA8943@infradead.org \
--to=hch@infradead.org \
--cc=clayne@anodized.com \
--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