From: David Chinner <dgc@sgi.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: Serious XFS crash
Date: Thu, 3 Apr 2008 08:07:50 +1000 [thread overview]
Message-ID: <20080402220750.GJ103491721@sgi.com> (raw)
In-Reply-To: <20080402133003.4bb043e4@galadriel.home>
On Wed, Apr 02, 2008 at 01:30:03PM +0200, Emmanuel Florac wrote:
> Le Wed, 2 Apr 2008 15:58:31 +1000 vous écriviez:
>
> > The log is rather garbled - can you repost? Also, XFS usually outputs
> > an error message before the stack trace; can you make sure you
> > paste that as well (if it exists)?
>
> Well I attached the relevant part of kern.log; the message just before
> the crash is not very clear... You can see the other messages relevant
> to the disk error too.
Like the fact reiser is also complaining about corrupted blocks?
> Mar 6 06:25:04 system3 kernel: 3w-9xxx: scsi0: AEN: WARNING (0x04:0x0023): Sector repair completed:port=6, LBA=0xE6E2A.
> Mar 6 06:25:04 system3 kernel: ReiserFS: warning: is_tree_node: node level 28784 does not match to the expected one 1
> Mar 6 06:25:04 system3 kernel: ReiserFS: sda1: warning: vs-5150: search_by_key: invalid format found in block 753671. Fsck?
> Mar 6 06:25:04 system3 kernel: ReiserFS: sda1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [18404 18463 0x0 SD]
and:
> Mar 6 10:42:46 system3 kernel: 0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Mar 6 10:42:46 system3 kernel: Filesystem "md0": XFS internal error xfs_alloc_read_agf at line 2190 of file fs/xfs/xfs_alloc.c. Caller 0xc01f4b88
That's an AGF made up of zeros instead of real metadata. Something has
trashed it - perhaps a "sector repair"?
> Mar 6 10:42:46 system3 kernel: Please umount the filesystem, and rectify the problem(s)
> Mar 6 10:51:19 system3 kernel: 3w-9xxx: scsi0: AEN: WARNING (0x04:0x0023): Sector repair completed:port=6, LBA=0xE6E00.
> Mar 6 10:51:20 system3 kernel: 3w-9xxx: scsi0: AEN: WARNING (0x04:0x0023): Sector repair completed:port=6, LBA=0xE6DCA.
I'd go and find whatever disk is located at LBA 0xE6DCA-0xE6E2A and
replace it - if there are that many repairs needed on it, it's likely
to be failing....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-02 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 17:54 Serious XFS crash Emmanuel Florac
2008-03-25 18:49 ` Eric Sandeen
2008-03-25 19:03 ` Emmanuel Florac
2008-03-25 23:36 ` David Chinner
2008-03-26 7:51 ` Emmanuel Florac
2008-03-26 20:13 ` Emmanuel Florac
2008-04-01 12:00 ` Emmanuel Florac
2008-04-02 5:58 ` David Chinner
2008-04-02 11:30 ` Emmanuel Florac
2008-04-02 22:07 ` David Chinner [this message]
2008-04-02 22:22 ` Emmanuel Florac
2008-04-03 0:49 ` David Chinner
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=20080402220750.GJ103491721@sgi.com \
--to=dgc@sgi.com \
--cc=eflorac@intellique.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