From: Eric Sandeen <sandeen@sandeen.net>
To: George Barnett <george@alink.co.za>
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruption on ubuntu 2.6.27-9-server
Date: Tue, 03 Feb 2009 19:28:23 -0600 [thread overview]
Message-ID: <4988EF37.7020306@sandeen.net> (raw)
In-Reply-To: <2653B83E-85DA-4949-BCED-AF2BA3D324E1@alink.co.za>
George Barnett wrote:
> Hi,
>
> I'm seeing the following errors:
>
> [822153.422851] Filesystem "md2": XFS internal error xfs_da_do_buf(2)
> at line 2107 of file /build/buildd/linux-2.6.27/fs/xfs/
we really should make that more informative.
What it means is that you read a piece of metadata that did not match
any of the metadata magic numbers.
hard to say whether it might be an xfs bug I think; this does come up
occasionally though and it'd at least be nice to print more details on
the error (what the magic *was*, what block, etc)
Do you happen to have the repair output?
Did your md raid lose power w/ write cache enabled?
-Eric
> xfs_da_btree.c. Caller 0xffffffffa03be8da
> [822153.422903] Pid: 3273, comm: du Not tainted 2.6.27-9-server #1
> [822153.422905]
> [822153.422906] Call Trace:
> [822153.422931] [<ffffffffa03cab23>] xfs_error_report+0x43/0x50 [xfs]
> [822153.422956] [<ffffffffa03be8da>] ? xfs_da_read_buf+0x2a/0x30 [xfs]
> [822153.422976] [<ffffffffa03cab8d>] xfs_corruption_error+0x5d/0x80
> [xfs]
> [822153.422995] [<ffffffffa03be808>] xfs_da_do_buf+0x6a8/0x700 [xfs]
> [822153.423014] [<ffffffffa03be8da>] ? xfs_da_read_buf+0x2a/0x30 [xfs]
> [822153.423019] [<ffffffff80305b06>] ? mntput_no_expire+0x36/0x160
> [822153.423022] [<ffffffff803866e1>] ? aa_permission+0x21/0xd0
> [822153.423041] [<ffffffffa03be8da>] xfs_da_read_buf+0x2a/0x30 [xfs]
> [822153.423061] [<ffffffffa03c34fa>] ? xfs_dir2_block_getdents+0x9a/
> 0x210 [xfs]
> [822153.423080] [<ffffffffa03c34fa>] xfs_dir2_block_getdents+0x9a/
> 0x210 [xfs]
> [822153.423099] [<ffffffffa03adf7b>] ? xfs_bmap_last_offset+0x13b/
> 0x150 [xfs]
> [822153.423119] [<ffffffffa03f9970>] ? xfs_hack_filldir+0x0/0x60 [xfs]
> [822153.423138] [<ffffffffa03f9970>] ? xfs_hack_filldir+0x0/0x60 [xfs]
> [822153.423157] [<ffffffffa03c148b>] xfs_readdir+0x9b/0xf0 [xfs]
> [822153.423176] [<ffffffffa03f98a6>] xfs_file_readdir+0xd6/0x1a0 [xfs]
> [822153.423180] [<ffffffff802f8810>] ? filldir+0x0/0xe0
> [822153.423183] [<ffffffff80386821>] ? aa_file_permission+0x21/0xf0
> [822153.423185] [<ffffffff802f8810>] ? filldir+0x0/0xe0
> [822153.423188] [<ffffffff802f8810>] ? filldir+0x0/0xe0
> [822153.423191] [<ffffffff802f8a9b>] vfs_readdir+0xbb/0xe0
> [822153.423194] [<ffffffff802f8c28>] sys_getdents+0x88/0xe0
> [822153.423199] [<ffffffff8021285a>] system_call_fastpath+0x16/0x1b
>
> This seems to happen reasonably regularly on my system and causes the
> filesystem to be marked as dirty. xfs_repair runs fine, but I end up
> with a bunch of files moved to lost+found. There are no device errors
> logged when this happens.
>
> Mount options:
>
> /dev/md2 on /data type xfs (rw,noatime)
>
> Kernel:
>
> Linux slut 2.6.27-9-server #1 SMP Thu Nov 20 22:56:07 UTC 2008 x86_64
> GNU/Linux
>
> Device:
>
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
> [raid4] [raid10]
> md2 : active raid10 sda2[0] sdd2[3] sdb2[1]
> 1947655680 blocks super 1.2 128K chunks 2 far-copies [4/3] [UUUU]
>
> # xfs_info /dev/md2
> meta-data=/dev/md2 isize=256 agcount=32,
> agsize=15216064 blks
> = sectsz=512 attr=0
> data = bsize=4096 blocks=486913920,
> imaxpct=25
> = sunit=32 swidth=128 blks
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=32768, version=1
> = sectsz=512 sunit=0 blks, lazy-
> count=0
> realtime =none extsz=524288 blocks=0, rtextents=0
>
> Any assistance would be greatly appreciated.
>
> George
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-04 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 0:32 XFS corruption on ubuntu 2.6.27-9-server George Barnett
2009-02-04 1:28 ` Eric Sandeen [this message]
2009-02-04 1:34 ` George Barnett
2009-02-04 1:46 ` Eric Sandeen
2009-02-04 1:53 ` George Barnett
2009-02-04 2:05 ` Eric Sandeen
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=4988EF37.7020306@sandeen.net \
--to=sandeen@sandeen.net \
--cc=george@alink.co.za \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.