| View previous topic :: View next topic |
| Author |
Message |
Crisis
l33t
Joined: 10 Feb 2003
Posts: 613
Location: Portland, OR
|
 Posted: Thu Sep 14, 2006 4:35 pm Post subject: XFS md raid5 internal error XFS_WANT_CORRUPTED_RETURN ? |
 |
|
I have a raid5 array with 8 drives, setup with md. Today it started to act slow, so looking at dmesg it was getting read errors on /dev/sdi. I ran smartctl on /dev/sdi which didn't find any errors, but eventually I just failed the drive and removed it fromt he raid array.
That seemed to fix it, but now I am getting this in my messages:
| Code: | Sep 14 09:29:56 anubis Call Trace: <ffffffff80310180>{xfs_alloc_fixup_trees+696}
Sep 14 09:29:56 anubis <ffffffff803115f9>{xfs_alloc_ag_vextent+1834} <ffffffff80312563>{xfs_alloc_vextent+685}
Sep 14 09:29:56 anubis <ffffffff8032074c>{xfs_bmapi+3945} <ffffffff8031e60d>{xfs_bmap_search_multi_extents+151}
Sep 14 09:29:56 anubis <ffffffff8034333b>{xfs_iomap_write_allocate+540} <ffffffff80259546>{slab_destroy+110}
Sep 14 09:29:56 anubis <ffffffff803426ae>{xfs_iomap+714} <ffffffff803592fc>{xfs_map_blocks+42}
Sep 14 09:29:56 anubis <ffffffff8035994a>{xfs_page_state_convert+698} <ffffffff802593ad>{kmem_freepages+187}
Sep 14 09:29:56 anubis <ffffffff8035a24d>{xfs_vm_writepage+167} <ffffffff802483de>{pageout+289}
Sep 14 09:29:56 anubis <ffffffff80248d26>{shrink_zone+1936} <ffffffff8024956d>{balance_pgdat+568}
Sep 14 09:29:56 anubis <ffffffff802350fa>{finish_wait+1} <ffffffff802497cf>{kswapd+269}
Sep 14 09:29:56 anubis <ffffffff80235143>{autoremove_wake_function+0} <ffffffff80235143>{autoremove_wake_function+0}
Sep 14 09:29:56 anubis <ffffffff80209e5e>{child_rip+8} <ffffffff802496c2>{kswapd+0}
Sep 14 09:29:56 anubis <ffffffff80209e56>{child_rip+0}
Sep 14 09:29:56 anubis XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff803115f9
|
Anyone have any ideas? |
|
| Back to top |
|
 |
Crisis
l33t
Joined: 10 Feb 2003
Posts: 613
Location: Portland, OR
|
| Posted: Thu Sep 14, 2006 11:29 pm Post subject: |
|
|
They could just be delayed errors from the drive being failed over, they have stopped and everything seems OK for now. (Although I'm starting to curse these samsung drives that keep failing...)  |
|
| Back to top |
|
|
zieloo
Veteran
Joined: 28 Mar 2004
Posts: 1337
|
| Posted: Wed Oct 18, 2006 2:54 pm Post subject: |
|
|
There must be something wrong with the filesystem structure. Unmount it, and issue:
but only if you're still getting those messages after removal of the disk. |
|
| Back to top |
|
|
|
Kernel & Hardware
