On Tue, Dec 21, 2010 at 07:41:51PM +0530, naveen yadav wrote:
> Hi all,
>
> We have one disk that got corrupted, when I connect to my PC, haveing
> kernel version(2.6.35.9).
> The Disk mount well, but when i do 'ls; command it hangs.
ls shouldn't hang. This should return:
> Please find the dmesg.
> /0x22 [xfs]
> [<e0dfd2c2>] xfs_da_do_buf+0x582/0x628 [xfs]
> [<e0dfd3ce>] ? xfs_da_read_buf+0x1d/0x22 [xfs]
> [<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [xfs]
> [<e0dfd3ce>] ? xfs_da_read_buf+0x1d/0x22 [xfs]
> [<e0dfd3ce>] xfs_da_read_buf+0x1d/0x22 [xfs]
> [<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [xfs]
> [<e0dfe0d3>] xfs_da_node_lookup_int+0x52/0x207 [xfs]
> [<e0e03888>] xfs_dir2_node_lookup+0x5f/0xee [xfs]
> [<e0dff26a>] xfs_dir_lookup+0xde/0x110 [xfs]
> [<e0e22c0a>] xfs_lookup+0x50/0x9f [xfs]
> [<e0e2c5a6>] xfs_vn_lookup+0x3e/0x76 [xfs]
> [<c04da3b2>] do_lookup+0xc9/0x139
> [<c04daabd>] link_path_walk+0x326/0x44d
> [<c043b145>] ? default_wake_function+0x10/0x12
> [<c04daca2>] path_walk+0x3f/0x89
> [<c04dc125>] ? path_init+0x9e/0x10c
> [<c04dc1b9>] do_path_lookup+0x26/0x74
> [<c04dcf95>] user_path_at+0x46/0x6c
> [<c0454687>] ? remove_wait_queue+0x27/0x2c
> [<c0430e9f>] ? spin_unlock_irqrestore+0xd/0xf
> [<c0431016>] ? __wake_up+0x37/0x40
> [<c04d645a>] vfs_fstatat+0x32/0x59
> [<c04d2bc4>] ? fsnotify_modify+0x54/0x5f
> [<c04d64cf>] vfs_lstat+0x1b/0x1d
> [<c04d64ea>] sys_lstat64+0x19/0x2d
> [<c04d3308>] ? vfs_write+0xb5/0xf4
> [<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
> [<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
> [<c0407fd8>] sysenter_do_call+0x12/0x2d
> c2d9d000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> Filesystem "sdb2": XFS internal error xfs_da_do_buf(2) at line 2113 of
> file fs/xfs/xfs_da_btree.c. Caller 0xe0dfd3ce
an EIO or EUCLEAN error to ls as it encountered a corrupted
directory block. Can you post the output of:
# echo w > /proc/sysrq-trigger
to show us where it has hung?
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
|