http://oss.sgi.com/bugzilla/show_bug.cgi?id=909
Summary: XFS internal error xfs_bmap_read_extents()
Product: XFS
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: XFS kernel code
AssignedTo: xfs-masters@xxxxxxxxxxx
ReportedBy: nbigaouette@xxxxxxxxx
Estimated Hours: 0.0
Classification: Unclassified
Created an attachment (id=303)
--> (http://oss.sgi.com/bugzilla/attachment.cgi?id=303)
dmesg output showing the crash.
We had some issues with physical hard drives in a raid 60 configuration (40TB)
with a single XFS partition on it. These issues were fixed by the hardware
vendor and the raid array was shipped back.
After re-installation, a user decided to do some cleanup on the raid partition.
He "rm -fr /raid/user/some_folder" but then rm reported an error that it
couldn't find the files/folder. Checking dmesg, it seems xfs crashed. Here is
the relevant output from dmesg:
[...]
[64568.732194] Filesystem "sdb1": corrupt dinode 271560310, (btree extents).
Unmount and run xfs_repair.
[64568.732201] Filesystem "sdb1": XFS internal error xfs_bmap_read_extents(1)
at line 4648 of file fs/xfs/xfs_bmap.c. Caller 0xffffffff812255ef
[64568.732204]
[64568.732207] Pid: 15370, comm: rm Not tainted 2.6.32-gentoo-r18-nb #3
[64568.732209] Call Trace:
[64568.732217] [<ffffffff8121e1e3>] xfs_error_report+0x3c/0x3e
[64568.732222] [<ffffffff812255ef>] ? xfs_iread_extents+0xb3/0xd2
[64568.732227] [<ffffffff8120af80>] xfs_bmap_read_extents+0x268/0x2f9
[64568.732231] [<ffffffff812255ef>] xfs_iread_extents+0xb3/0xd2
[64568.732235] [<ffffffff8120bc43>] xfs_bunmapi+0x115/0x738
[64568.732239] [<ffffffff8122b10e>] ? xfs_log_release_iclog+0x18/0x43
[64568.732244] [<ffffffff8123b057>] ? kmem_zone_alloc+0x67/0xaf
[64568.732247] [<ffffffff8123b0be>] ? kmem_zone_zalloc+0x1f/0x30
[64568.732252] [<ffffffff81224dae>] xfs_itruncate_finish+0x160/0x285
[64568.732256] [<ffffffff81239a90>] xfs_inactive+0x1c3/0x3ae
[64568.732261] [<ffffffff810eb755>] ? fsnotify_clear_marks_by_inode+0x28/0xdd
[64568.732267] [<ffffffff81242ec0>] xfs_fs_clear_inode+0x67/0x69
[64568.732273] [<ffffffff810d4f6a>] clear_inode+0x74/0xcd
[64568.732277] [<ffffffff810d56ef>] generic_delete_inode+0xf6/0x16b
[64568.732281] [<ffffffff810d577b>] generic_drop_inode+0x17/0x62
[64568.732285] [<ffffffff810d47e4>] iput+0x61/0x65
[64568.732289] [<ffffffff810ce021>] do_unlinkat+0x102/0x158
[64568.732293] [<ffffffff810d0159>] ? sys_getdents+0xb4/0xc4
[64568.732297] [<ffffffff810ce1aa>] sys_unlinkat+0x24/0x26
[64568.732301] [<ffffffff8100baab>] system_call_fastpath+0x16/0x1b
[64568.732309] Filesystem "sdb1": XFS internal error xfs_trans_cancel at line
1162 of file fs/xfs/xfs_trans.c. Caller 0xffffffff81239c07
[64568.732312]
[64568.732314] Pid: 15370, comm: rm Not tainted 2.6.32-gentoo-r18-nb #3
[64568.732316] Call Trace:
[64568.732320] [<ffffffff8121e1e3>] xfs_error_report+0x3c/0x3e
[64568.732323] [<ffffffff81239c07>] ? xfs_inactive+0x33a/0x3ae
[64568.732328] [<ffffffff81234e8b>] xfs_trans_cancel+0x5f/0xe3
[64568.732331] [<ffffffff81239c07>] xfs_inactive+0x33a/0x3ae
[64568.732335] [<ffffffff810eb755>] ? fsnotify_clear_marks_by_inode+0x28/0xdd
[64568.732340] [<ffffffff81242ec0>] xfs_fs_clear_inode+0x67/0x69
[64568.732343] [<ffffffff810d4f6a>] clear_inode+0x74/0xcd
[64568.732347] [<ffffffff810d56ef>] generic_delete_inode+0xf6/0x16b
[64568.732351] [<ffffffff810d577b>] generic_drop_inode+0x17/0x62
[64568.732355] [<ffffffff810d47e4>] iput+0x61/0x65
[64568.732359] [<ffffffff810ce021>] do_unlinkat+0x102/0x158
[64568.732363] [<ffffffff810d0159>] ? sys_getdents+0xb4/0xc4
[64568.732366] [<ffffffff810ce1aa>] sys_unlinkat+0x24/0x26
[64568.732370] [<ffffffff8100baab>] system_call_fastpath+0x16/0x1b
[64568.732374] xfs_force_shutdown(sdb1,0x8) called from line 1163 of file
fs/xfs/xfs_trans.c. Return address = 0xffffffff81234ea4
[64568.732494] Filesystem "sdb1": Corruption of in-memory data detected.
Shutting down filesystem: sdb1
[64568.732497] Please umount the filesystem, and rectify the problem(s)
[64582.718015] Filesystem "sdb1": xfs_log_force: error 5 returned.
[64586.593159] nfsd: non-standard errno: 5
[64586.594064] nfsd: non-standard errno: 5
[64586.594420] nfsd: non-standard errno: 5
[64586.594832] nfsd: non-standard errno: 5
[64586.595352] nfsd: non-standard errno: 5
[64586.595816] nfsd: non-standard errno: 5
[64586.596157] nfsd: non-standard errno: 5
[64586.596617] nfsd: non-standard errno: 5
[64612.672292] Filesystem "sdb1": xfs_log_force: error 5 returned.
[...]
I will unmount the drive and might check it with xfs_repair, but xfs should not
crash.
Also, will it be "safe" to keep that machine up? If the filesystem is repaired
correctly, will the kernel be able to mount the drive or the crash made the
kernel un-usable?
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
|