From: Eric Sandeen <sandeen@sandeen.net>
To: slaton <slaton@berkeley.edu>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO)
Date: Mon, 25 Feb 2008 14:40:17 -0800 [thread overview]
Message-ID: <47C343D1.30304@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0802221718430.13471@toro.qb3.berkeley.edu>
slaton wrote:
> A RAID5 (3ware card w/ 8 drive cage) filesystem on our cluster login node
> shut down the other night with this error:
>
> kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
> fs/xfs/xfs_alloc.c. Caller 0xffffffff8812b3a3
> kernel: Call Trace: [<ffffffff88129713>] [<ffffffff8812b3a3>]
> kernel: [<ffffffff88150df7>] [<ffffffff8816af8a>]
> [<ffffffff88137d6c>]
> kernel: [<ffffffff88157d25>] [<ffffffff8816ed1c>]
> [<ffffffff811051fa>]
> kernel: [<ffffffff8817a5b2>] [<ffffffff8102c988>]
> [<ffffffff882566ee>]
> kernel: [<ffffffff8825ba4d>] [<ffffffff8825170a>]
> [<ffffffff881a379e>]
> kernel: [<ffffffff882512da>] [<ffffffff882514a0>]
> [<ffffffff810604e2>]
> kernel: [<ffffffff882512da>] [<ffffffff882512da>]
> [<ffffffff810604da>]
> kernel: xfs_force_shutdown(sda1,0x8) called from line 4091 of file
> fs/xfs/xfs_bmap.c. Return address = 0xffffffff88137daf
> kernel: Filesystem "sda1": Corruption of in-memory data detected.
> Shutting down filesystem: sda1
> kernel: Please umount the filesystem, and rectify the problem(s)
> kernel: nfsd: non-standard errno: -990
>
> System hung upon attempting to umount the volume. Have not yet rebooted.
>
> Some additional info:
>
> - Server arch is x86_64 (smp).
>
> - Distro is caos2 linux, kernel 2.6.17 (smp). 2.6.23 pkg is also
> available.
ksymoops might be good so we can see what the actual backtrace was.
Are you hitting http://oss.sgi.com/projects/xfs/faq.html#dir2 ?
-Eric
next prev parent reply other threads:[~2008-02-25 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:20 Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) slaton
2008-02-25 22:40 ` Eric Sandeen [this message]
2008-02-26 7:54 ` slaton
2008-02-27 22:44 ` slaton
2008-02-28 3:16 ` Barry Naujok
2008-03-01 4:09 ` slaton
2008-03-04 1:29 ` slaton
2008-03-04 1:36 ` Barry Naujok
2008-03-04 1:43 ` slaton
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=47C343D1.30304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=slaton@berkeley.edu \
--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