From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair 3.1.2 crashing
Date: Sat, 12 Jun 2010 12:41:48 +0200 [thread overview]
Message-ID: <201006121241.52336@zmi.at> (raw)
In-Reply-To: <4C12E520.6040008@sandeen.net>
[-- Attachment #1.1: Type: Text/Plain, Size: 10944 bytes --]
On Samstag, 12. Juni 2010 Eric Sandeen wrote:
> > du: cannot access
> > `samba/backup/uranus/WindowsImageBackup/uranus/Backup 2010-06-05
> > 010014/852c2690-cf1a-11de-b09b-806e6f6e6963.vhd': Structure needs
> > cleaning
> dmesg would be the right thing to do here ...
There are a lot, here the last two:
[157312.699958] XFS mounting filesystem dm-0
[157312.891010] Ending clean XFS mount for filesystem: dm-0
[157340.953238] Filesystem "dm-0": corrupt inode 2195133988 ((a)extents = 5). Unmount and run xfs_repair.
[157340.953250] ffff8800928b6400: 49 4e 81 c0 02 02 00 00 00 00 03 e8 00 00 00 64 IN.............d
[157340.953268] Filesystem "dm-0": XFS internal error xfs_iformat_extents(1) at line 558 of file /usr/src/packages/BUILD/kernel-desktop-2.6.31.12/linux-2.6.31/fs/xfs/xfs_inode.c. Caller 0xffffffffa03380ad
[157340.953271]
[157340.953285] Pid: 27034, comm: du Not tainted 2.6.31.12-0.2-desktop #1
[157340.953292] Call Trace:
[157340.953308] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0
[157340.953316] [<ffffffff8101025d>] dump_trace+0xad/0x3a0
[157340.953324] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90
[157340.953331] [<ffffffff81011573>] show_trace+0x23/0x40
[157340.953339] [<ffffffff81552b46>] dump_stack+0x81/0x9e
[157340.953369] [<ffffffffa032db4a>] xfs_error_report+0x5a/0x70 [xfs]
[157340.953427] [<ffffffffa032dbcc>] xfs_corruption_error+0x6c/0x90 [xfs]
[157340.953482] [<ffffffffa0337b84>] xfs_iformat_extents+0x234/0x280 [xfs]
[157340.953543] [<ffffffffa03380ad>] xfs_iformat+0x28d/0x5a0 [xfs]
[157340.953600] [<ffffffffa0338542>] xfs_iread+0x182/0x1c0 [xfs]
[157340.953658] [<ffffffffa0333938>] xfs_iget_cache_miss+0x78/0x250 [xfs]
[157340.953712] [<ffffffffa0333c3c>] xfs_iget+0x12c/0x1b0 [xfs]
[157340.953768] [<ffffffffa0353b8e>] xfs_lookup+0xce/0x100 [xfs]
[157340.953843] [<ffffffffa0360e6c>] xfs_vn_lookup+0x6c/0xc0 [xfs]
[157340.953922] [<ffffffff81157782>] real_lookup+0x102/0x180
[157340.953931] [<ffffffff811598c0>] do_lookup+0xd0/0x100
[157340.953938] [<ffffffff81159e12>] __link_path_walk+0x522/0x880
[157340.953945] [<ffffffff8115a6f6>] path_walk+0x66/0xd0
[157340.953953] [<ffffffff8115a7cb>] do_path_lookup+0x6b/0xb0
[157340.953957] [<ffffffff8115a9d1>] user_path_at+0x61/0xc0
[157340.953962] [<ffffffff811514d1>] vfs_fstatat+0x41/0x90
[157340.953967] [<ffffffff81151549>] sys_newfstatat+0x29/0x60
[157340.953973] [<ffffffff8100c682>] system_call_fastpath+0x16/0x1b
[157340.953986] [<00007fd51c9e50ee>] 0x7fd51c9e50ee
[157573.164556] Filesystem "dm-0": corrupt inode 2195133988 ((a)extents = 5). Unmount and run xfs_repair.
[157573.164584] ffff8800928b6400: 49 4e 81 c0 02 02 00 00 00 00 03 e8 00 00 00 64 IN.............d
[157573.164608] Filesystem "dm-0": XFS internal error xfs_iformat_extents(1) at line 558 of file /usr/src/packages/BUILD/kernel-desktop-2.6.31.12/linux-2.6.31/fs/xfs/xfs_inode.c. Caller 0xffffffffa03380ad
[157573.164615]
[157573.164646] Pid: 27064, comm: du Not tainted 2.6.31.12-0.2-desktop #1
[157573.164659] Call Trace:
[157573.164688] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0
[157573.164710] [<ffffffff8101025d>] dump_trace+0xad/0x3a0
[157573.164729] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90
[157573.164747] [<ffffffff81011573>] show_trace+0x23/0x40
[157573.164765] [<ffffffff81552b46>] dump_stack+0x81/0x9e
[157573.164833] [<ffffffffa032db4a>] xfs_error_report+0x5a/0x70 [xfs]
[157573.164988] [<ffffffffa032dbcc>] xfs_corruption_error+0x6c/0x90 [xfs]
[157573.165151] [<ffffffffa0337b84>] xfs_iformat_extents+0x234/0x280 [xfs]
[157573.165317] [<ffffffffa03380ad>] xfs_iformat+0x28d/0x5a0 [xfs]
[157573.165477] [<ffffffffa0338542>] xfs_iread+0x182/0x1c0 [xfs]
[157573.165640] [<ffffffffa0333938>] xfs_iget_cache_miss+0x78/0x250 [xfs]
[157573.165794] [<ffffffffa0333c3c>] xfs_iget+0x12c/0x1b0 [xfs]
[157573.165951] [<ffffffffa0353b8e>] xfs_lookup+0xce/0x100 [xfs]
[157573.166169] [<ffffffffa0360e6c>] xfs_vn_lookup+0x6c/0xc0 [xfs]
[157573.166366] [<ffffffff81157782>] real_lookup+0x102/0x180
[157573.166387] [<ffffffff811598c0>] do_lookup+0xd0/0x100
[157573.166406] [<ffffffff81159e12>] __link_path_walk+0x522/0x880
[157573.166425] [<ffffffff8115a6f6>] path_walk+0x66/0xd0
[157573.166443] [<ffffffff8115a7cb>] do_path_lookup+0x6b/0xb0
[157573.166461] [<ffffffff8115a9d1>] user_path_at+0x61/0xc0
[157573.166481] [<ffffffff811514d1>] vfs_fstatat+0x41/0x90
[157573.166500] [<ffffffff81151549>] sys_newfstatat+0x29/0x60
[157573.166520] [<ffffffff8100c682>] system_call_fastpath+0x16/0x1b
[157573.166551] [<00007f63d57480ee>] 0x7f63d57480ee
> > xfs_repair version 3.1.2
> which kernel, again? The fork offset problems smell like something
> that's fixed.
openSUSE 11.2 with it's latest kernel, 2.6.31.12-0.2-desktop
But as I said: fresh disks, fresh XFS, copied from another server with rsync, no crashes,
not even a reboot. Why the problems?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-12 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:06 xfs_repair 3.1.2 crashing Michael Monnerie
2010-06-10 16:27 ` Eric Sandeen
2010-06-11 23:38 ` Michael Monnerie
2010-06-12 1:38 ` Eric Sandeen
2010-06-12 10:41 ` Michael Monnerie [this message]
2010-06-23 18:32 ` Michael Monnerie
2010-06-12 13:33 ` Michael Monnerie
2010-06-14 12:47 ` Michael Monnerie
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=201006121241.52336@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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