From: Emmanuel Florac <eflorac@intellique.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Serious XFS crash
Date: Tue, 1 Apr 2008 14:00:35 +0200 [thread overview]
Message-ID: <20080401140035.46470306@galadriel.home> (raw)
In-Reply-To: <20080325233611.GW103491721@sgi.com>
Le Wed, 26 Mar 2008 10:36:11 +1100 vous écriviez:
> What sector size is being used for the XFS filesystem? If it's
> not the same as teh filesystem block size, then XFS can't have done
> this itself because the offset that this garbage starts at would
> not be block aligned.....
I've gone thru the logs. This machine had a serious XFS crash on march
6 due to bad blocks (failed drive in the RAID-5). Is it possible that
the March 19 XFS crash is related to this, i. e. after running
xfs_repair on march 6 it remained some on-disk garbage that provoked a
new crash a couple of weeks later?
Here is the march 6 crash :
Mar 6 10:42:46 system3 kernel: [xfs_alloc_read_agf+244/432]
xfs_alloc_read_agf+0xf4/0x1b0 Mar 6 10:42:46 system3 kernel:
[xfs_alloc_fix_freelist+1000/1120] xfs_alloc_fix_freelist+0x3e8/0x460
Mar 6 10:42:46 system3 last message repeated 2 times Mar 6 10:42:46
system3 kernel: [_xfs_trans_commit+489/928]
_xfs_trans_commit+0x1e9/0x3a0 Mar 6 10:42:46 system3 kernel:
[xfs_free_extent+152/224] xfs_free_extent+0x98/0xe0 Mar 6 10:42:46
system3 kernel: [xfs_bmap_finish+263/400] xfs_bmap_finish+0x107/0x190
Mar 6 10:42:46 system3 kernel: [xfs_itruncate_finish+544/976]
xfs_itruncate_finish+0x220/0x3d0 Mar 6 10:42:46 system3 kernel:
[xfs_trans_ijoin+43/128] xfs_trans_ijoin+0x2b/0x80 Mar 6 10:42:46
system3 kernel: [xfs_inactive+1195/1296] xfs_inactive+0x4ab/0x510 Mar
6 10:42:46 system3 kernel: [xfs_fs_clear_inode+156/192]
xfs_fs_clear_inode+0x9c/0xc0 Mar 6 10:42:46 system3 kernel:
[invalidate_inode_buffers+21/112] invalidate_inode_buffers+0x15/0x70
Mar 6 10:42:46 system3 kernel: [clear_inode+212/320]
clear_inode+0xd4/0x140 Mar 6 10:42:46 system3 kernel:
[truncate_inode_pages+23/32] truncate_inode_pages+0x17/0x20 Mar 6
10:42:46 system3 kernel: [generic_delete_inode+264/272]
generic_delete_inode+0x108/0x110 Mar 6 10:42:46 system3 kernel:
[iput+83/112] iput+0x53/0x70 Mar 6 10:42:46 system3 kernel:
[do_unlinkat+186/272] do_unlinkat+0xba/0x110 Mar 6 10:42:46 system3
kernel: [sys_fcntl64+89/144] sys_fcntl64+0x59/0x90 Mar 6 10:42:46
system3 kernel: [syscall_call+7/11] syscall_call+0x7/0xb Mar 6
10:42:46 system3 kernel: xfs_force_shutdown(md0,0x8) called from line
4267 of file fs/xfs/xfs_bmap.c. Return address = 0xc0256b29 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.
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
next prev parent reply other threads:[~2008-04-01 12:00 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 [this message]
2008-04-02 5:58 ` David Chinner
2008-04-02 11:30 ` Emmanuel Florac
2008-04-02 22:07 ` David Chinner
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=20080401140035.46470306@galadriel.home \
--to=eflorac@intellique.com \
--cc=dgc@sgi.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