From: David Chinner <dgc@sgi.com>
To: Christian Schmid <webmaster@rapidforum.com>
Cc: xfs@oss.sgi.com
Subject: Re: Critical xfs bug in 2.6.17.11?
Date: Mon, 11 Sep 2006 10:54:29 +1000 [thread overview]
Message-ID: <20060911005429.GK10950339@melbourne.sgi.com> (raw)
In-Reply-To: <4504151F.6050704@rapidforum.com>
On Sun, Sep 10, 2006 at 03:37:35PM +0200, Christian Schmid wrote:
> Hello.
>
> Instead of a tmpfs, I use a raid 10 softraid. Unfortunately it crashed
> after 10 hours of extreme activities (read/block-writes with up to 250
> streams/deletes)
>
> 12 gb memory-test successful. 2 cpu xeon smp system.
>
> Tell me if this helps you:
>
> Sep 9 18:08:49 inode430 kernel: [87433.143498] 0x0: 58 41 47 46 00 00 00
> 01 00 00 00 00 00 04 34 a0
> Sep 9 18:08:49 inode430 kernel: [87433.143672] Filesystem "md5": XFS
> internal error xfs_alloc_read_agf at line 2176 of file fs/xfs/xfs_alloc.c.
> Caller 0xffffffff80314069
Hmm - bad read of the AGF during allocation, which causes a shutdown
due to cancelling a dirty transaction.
If you run "xfs_check -n /dev/md5" and "xfs_repair -n /dev/md5" do
they warn about any AGF related corruption?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-09-11 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 13:37 Critical xfs bug in 2.6.17.11? Christian Schmid
2006-09-10 21:31 ` Justin Piszcz
2006-09-10 22:13 ` Christian Schmid
2006-09-10 22:37 ` Justin Piszcz
2006-09-10 23:35 ` Christian Schmid
2006-09-11 1:00 ` David Chinner
2006-09-11 12:31 ` Christian Schmid
2006-09-11 0:54 ` David Chinner [this message]
2006-09-11 12:29 ` Christian Schmid
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=20060911005429.GK10950339@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=webmaster@rapidforum.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