From: Emmanuel Florac <eflorac@intellique.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Serious XFS crash
Date: Wed, 2 Apr 2008 13:30:03 +0200 [thread overview]
Message-ID: <20080402133003.4bb043e4@galadriel.home> (raw)
In-Reply-To: <20080402055831.GG103491721@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
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.
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
[-- Attachment #2: log --]
[-- Type: text/plain, Size: 2909 bytes --]
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]
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
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:42:46 system3 kernel: Filesystem "md0": Corruption of in-memory data detected. Shutting down filesystem: md0
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.
next prev parent reply other threads:[~2008-04-02 11:34 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 [this message]
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=20080402133003.4bb043e4@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