* Issue on kernel 2.6.35.9 vanilla
[not found] <AANLkTim8VD2NQ1a2t47jOA+MyyVGWejymoJh41jfrRkA@mail.gmail.com>
@ 2010-12-21 14:11 ` naveen yadav
2010-12-21 21:31 ` Dave Chinner
0 siblings, 1 reply; 5+ messages in thread
From: naveen yadav @ 2010-12-21 14:11 UTC (permalink / raw)
To: xfs
[-- Attachment #1: Type: text/plain, Size: 2521 bytes --]
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.
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
Pid: 2199, comm: ls Not tainted 2.6.35.9 #1
Call Trace:
[<e0e06460>] xfs_error_report+0x31/0x33 [xfs]
[<e0e064a0>] xfs_corruption_error+0x3e/0x48 [xfs]
[<e0dfd3ce>] ? xfs_da_read_buf+0x1d/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
[-- Attachment #2: log-2.6.35.9-ls-hang --]
[-- Type: application/octet-stream, Size: 14960 bytes --]
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
XFS mounting filesystem sdb2
Starting XFS recovery on filesystem: sdb2 (logdev: internal)
Ending XFS recovery on filesystem: sdb2 (logdev: internal)
SELinux: initialized (dev sdb2, type xfs), uses xattr
usb 1-2: USB disconnect, address 8
usb 1-2: new high speed USB device using ehci_hcd and address 9
usb 1-2: New USB device found, idVendor=0781, idProduct=5567
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: Cruzer Blade
usb 1-2: Manufacturer: SanDisk
usb 1-2: SerialNumber: 2005314630160C6014C6
scsi10 : usb-storage 1-2:1.0
scsi 10:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 2
sd 10:0:0:0: Attached scsi generic sg1 type 0
sd 10:0:0:0: [sdb] 15625216 512-byte logical blocks: (8.00 GB/7.45 GiB)
sd 10:0:0:0: [sdb] Write Protect is off
sd 10:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 10:0:0:0: [sdb] Assuming drive cache: write through
sd 10:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb2
sd 10:0:0:0: [sdb] Assuming drive cache: write through
sd 10:0:0:0: [sdb] Attached SCSI removable disk
XFS mounting filesystem sdb2
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
Starting XFS recovery on filesystem: sdb2 (logdev: internal)
Ending XFS recovery on filesystem: sdb2 (logdev: internal)
SELinux: initialized (dev sdb2, type xfs), uses xattr
INFO: task gvfs-gdu-volume:7514 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7514 1 0x00000080
d96c5b2c 00000086 d5e81fcf 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
de55dc34 c0a25e00 c0a25e00 0000d285 00000000 cd639200 00004465 de55d9b0
02000000 dd423208 dd423200 7fffffff 7fffffff d96c5b70 c0781c43 00000000
Call Trace:
[<c0781c43>] schedule_timeout+0x1b/0x95
[<c07824d1>] __down_common+0x82/0xb9
[<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
[<c0782567>] __down+0x17/0x19
[<c045827c>] down+0x27/0x37
[<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
[<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
[<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
[<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
[<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
[<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
[<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
[<c04dbd59>] do_last+0x186/0x49f
[<c04dc415>] do_filp_open+0x1bd/0x459
[<c045b191>] ? timekeeping_get_ns+0x16/0x54
[<c05a9170>] ? might_fault+0x1e/0x20
[<c04e479a>] ? alloc_fd+0x58/0xbe
[<c04d1941>] do_sys_open+0x4d/0xe4
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c04d1a24>] sys_open+0x23/0x2b
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfs-gdu-volume:7520 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7520 1 0x00000088
c7847dc0 00000086 d5eedb9e 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd789c24 c0a25e00 c0a25e00 00001168 00000000 de7a1e00 00004465 cd7899a0
00000001 c368b1a4 c368b19c cd7899a0 c368b1a0 c7847df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfsd-trash:1905 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfsd-trash D 00004466 0 1905 1 0x00000080
cd6e9dc0 00000086 117c11b1 00004466 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd6bb5c4 c0a25e00 c0a25e00 0065a38d 00000000 cd418c00 00004466 cd6bb340
00000000 c368b1a4 c368b19c cd6bb340 c368b1a0 cd6e9df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c05a20d8>] ? idr_get_empty_slot+0x144/0x216
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c04da268>] ? path_put+0x1a/0x1d
[<c04fa32f>] ? sys_inotify_add_watch+0x226/0x281
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
[<c0780000>] ? profile_cpu_callback+0xe0/0x197
INFO: task gvfs-gdu-volume:7514 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7514 1 0x00000080
d96c5b2c 00000086 d5e81fcf 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
de55dc34 c0a25e00 c0a25e00 0000d285 00000000 cd639200 00004465 de55d9b0
02000000 dd423208 dd423200 7fffffff 7fffffff d96c5b70 c0781c43 00000000
Call Trace:
[<c0781c43>] schedule_timeout+0x1b/0x95
[<c07824d1>] __down_common+0x82/0xb9
[<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
[<c0782567>] __down+0x17/0x19
[<c045827c>] down+0x27/0x37
[<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
[<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
[<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
[<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
[<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
[<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
[<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
[<c04dbd59>] do_last+0x186/0x49f
[<c04dc415>] do_filp_open+0x1bd/0x459
[<c045b191>] ? timekeeping_get_ns+0x16/0x54
[<c05a9170>] ? might_fault+0x1e/0x20
[<c04e479a>] ? alloc_fd+0x58/0xbe
[<c04d1941>] do_sys_open+0x4d/0xe4
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c04d1a24>] sys_open+0x23/0x2b
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfs-gdu-volume:7520 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7520 1 0x00000088
c7847dc0 00000086 d5eedb9e 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd789c24 c0a25e00 c0a25e00 00001168 00000000 de7a1e00 00004465 cd7899a0
00000001 c368b1a4 c368b19c cd7899a0 c368b1a0 c7847df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfsd-trash:1905 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfsd-trash D 00004466 0 1905 1 0x00000080
cd6e9dc0 00000086 117c11b1 00004466 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd6bb5c4 c0a25e00 c0a25e00 0065a38d 00000000 cd418c00 00004466 cd6bb340
00000000 c368b1a4 c368b19c cd6bb340 c368b1a0 cd6e9df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c05a20d8>] ? idr_get_empty_slot+0x144/0x216
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c04da268>] ? path_put+0x1a/0x1d
[<c04fa32f>] ? sys_inotify_add_watch+0x226/0x281
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
[<c0780000>] ? profile_cpu_callback+0xe0/0x197
INFO: task gvfs-gdu-volume:7514 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7514 1 0x00000080
d96c5b2c 00000086 d5e81fcf 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
de55dc34 c0a25e00 c0a25e00 0000d285 00000000 cd639200 00004465 de55d9b0
02000000 dd423208 dd423200 7fffffff 7fffffff d96c5b70 c0781c43 00000000
Call Trace:
[<c0781c43>] schedule_timeout+0x1b/0x95
[<c07824d1>] __down_common+0x82/0xb9
[<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
[<c0782567>] __down+0x17/0x19
[<c045827c>] down+0x27/0x37
[<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
[<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
[<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
[<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
[<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
[<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
[<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
[<c04dbd59>] do_last+0x186/0x49f
[<c04dc415>] do_filp_open+0x1bd/0x459
[<c045b191>] ? timekeeping_get_ns+0x16/0x54
[<c05a9170>] ? might_fault+0x1e/0x20
[<c04e479a>] ? alloc_fd+0x58/0xbe
[<c04d1941>] do_sys_open+0x4d/0xe4
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c04d1a24>] sys_open+0x23/0x2b
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfs-gdu-volume:7520 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7520 1 0x00000088
c7847dc0 00000086 d5eedb9e 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd789c24 c0a25e00 c0a25e00 00001168 00000000 de7a1e00 00004465 cd7899a0
00000001 c368b1a4 c368b19c cd7899a0 c368b1a0 c7847df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
INFO: task gvfsd-trash:1905 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfsd-trash D 00004466 0 1905 1 0x00000080
cd6e9dc0 00000086 117c11b1 00004466 c0a25e00 c0a25e00 c0a25e00 c0a25e00
cd6bb5c4 c0a25e00 c0a25e00 0065a38d 00000000 cd418c00 00004466 cd6bb340
00000000 c368b1a4 c368b19c cd6bb340 c368b1a0 cd6e9df4 c0782093 c368b1ac
Call Trace:
[<c0782093>] __mutex_lock_common+0xe8/0x137
[<c07820f9>] __mutex_lock_slowpath+0x17/0x1a
[<c07821e8>] ? mutex_lock+0x30/0x3e
[<c07821e8>] mutex_lock+0x30/0x3e
[<c04da370>] do_lookup+0x87/0x139
[<c04daabd>] link_path_walk+0x326/0x44d
[<c04daca2>] path_walk+0x3f/0x89
[<c04dc0f7>] ? path_init+0x70/0x10c
[<c04dc1b9>] do_path_lookup+0x26/0x74
[<c04dcf95>] user_path_at+0x46/0x6c
[<c05a20d8>] ? idr_get_empty_slot+0x144/0x216
[<c04d645a>] vfs_fstatat+0x32/0x59
[<c04d64cf>] vfs_lstat+0x1b/0x1d
[<c04d64ea>] sys_lstat64+0x19/0x2d
[<c04da268>] ? path_put+0x1a/0x1d
[<c04fa32f>] ? sys_inotify_add_watch+0x226/0x281
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c05a8cb8>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0407fd8>] sysenter_do_call+0x12/0x2d
[<c0780000>] ? profile_cpu_callback+0xe0/0x197
INFO: task gvfs-gdu-volume:7514 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gvfs-gdu-volu D 00004465 0 7514 1 0x00000080
d96c5b2c 00000086 d5e81fcf 00004465 c0a25e00 c0a25e00 c0a25e00 c0a25e00
de55dc34 c0a25e00 c0a25e00 0000d285 00000000 cd639200 00004465 de55d9b0
02000000 dd423208 dd423200 7fffffff 7fffffff d96c5b70 c0781c43 00000000
Call Trace:
[<c0781c43>] schedule_timeout+0x1b/0x95
[<c07824d1>] __down_common+0x82/0xb9
[<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
[<c0782567>] __down+0x17/0x19
[<c045827c>] down+0x27/0x37
[<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
[<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
[<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
[<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
[<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
[<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
[<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
[<c04dbd59>] do_last+0x186/0x49f
[<c04dc415>] do_filp_open+0x1bd/0x459
[<c045b191>] ? timekeeping_get_ns+0x16/0x54
[<c05a9170>] ? might_fault+0x1e/0x20
[<c04e479a>] ? alloc_fd+0x58/0xbe
[<c04d1941>] do_sys_open+0x4d/0xe4
[<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
[<c04d1a24>] sys_open+0x23/0x2b
[<c0407fd8>] sysenter_do_call+0x12/0x2d
usb 1-2: USB disconnect, address 9
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Issue on kernel 2.6.35.9 vanilla
2010-12-21 14:11 ` Issue on kernel 2.6.35.9 vanilla naveen yadav
@ 2010-12-21 21:31 ` Dave Chinner
[not found] ` <AANLkTik3batsHu57QDUWmspf7C8As75t3mUO6QG_i040@mail.gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Dave Chinner @ 2010-12-21 21:31 UTC (permalink / raw)
To: naveen yadav; +Cc: xfs
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Issue on kernel 2.6.35.9 vanilla
[not found] ` <AANLkTik3batsHu57QDUWmspf7C8As75t3mUO6QG_i040@mail.gmail.com>
@ 2010-12-22 4:57 ` naveen yadav
[not found] ` <20101222053730.GG4907@dastard>
1 sibling, 0 replies; 5+ messages in thread
From: naveen yadav @ 2010-12-22 4:57 UTC (permalink / raw)
To: Dave Chinner, xfs
On Wed, Dec 22, 2010 at 10:27 AM, naveen yadav <yad.naveen@gmail.com> wrote:
> Hi Dave,
>
> Please find attached log as suggested by you.
>
> Kind regards
> Naveen
>
> On Wed, Dec 22, 2010 at 3:01 AM, Dave Chinner <david@fromorbit.com> wrote:
>> 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@fromorbit.com
>>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Issue on kernel 2.6.35.9 vanilla
[not found] ` <20101222053730.GG4907@dastard>
@ 2010-12-22 7:00 ` naveen yadav
2010-12-23 5:19 ` naveen yadav
0 siblings, 1 reply; 5+ messages in thread
From: naveen yadav @ 2010-12-22 7:00 UTC (permalink / raw)
To: Dave Chinner, xfs
[-- Attachment #1: Type: text/plain, Size: 6750 bytes --]
Thanks a lot Dave,
Please find attached log for command xfs_repair -n.
Thanks a lot
On Wed, Dec 22, 2010 at 11:07 AM, Dave Chinner <david@fromorbit.com> wrote:
> On Wed, Dec 22, 2010 at 10:27:16AM +0530, naveen yadav wrote:
>> Hi Dave,
>>
>> Please find attached log as suggested by you.
>>
>> Kind regards
>> Naveen
>>
>> On Wed, Dec 22, 2010 at 3:01 AM, Dave Chinner <david@fromorbit.com> wrote:
>> > 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]
> .....
>> >> 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
>
> This is not in your dmesg log. When did it actually happen? Before
> the hung task timer started to trip? From your log:
>
> scsi 5:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 2
> sd 5:0:0:0: Attached scsi generic sg1 type 0
> sd 5:0:0:0: [sdb] 15625216 512-byte logical blocks: (8.00 GB/7.45 GiB)
> sd 5:0:0:0: [sdb] Write Protect is off
> sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
> sd 5:0:0:0: [sdb] Assuming drive cache: write through
> sd 5:0:0:0: [sdb] Assuming drive cache: write through
> sdb: sdb1 sdb2
> sd 5:0:0:0: [sdb] Assuming drive cache: write through
> sd 5:0:0:0: [sdb] Attached SCSI removable disk
> SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
> XFS mounting filesystem sdb2
> Starting XFS recovery on filesystem: sdb2 (logdev: internal)
> Ending XFS recovery on filesystem: sdb2 (logdev: internal)
> SELinux: initialized (dev sdb2, type xfs), uses xattr
> INFO: task gvfs-gdu-volume:2311 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> gvfs-gdu-volu D 00000026 0 2311 1 0x00000080
> c6cf9b2c 00000086 a41cc623 00000026 c0a25e00 c0a25e00 c0a25e00 c0a25e00
> d1290f54 c0a25e00 c0a25e00 000336ad 00000000 cd871c00 00000026 d1290cd0
> 00000000 cd8d2a08 cd8d2a00 7fffffff 7fffffff c6cf9b70 c0781c43 00000000
> Call Trace:
> [<c0781c43>] schedule_timeout+0x1b/0x95
> [<c07824d1>] __down_common+0x82/0xb9
> [<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
> [<c0782567>] __down+0x17/0x19
> [<c045827c>] down+0x27/0x37
> [<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
> [<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
> [<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
> [<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
> [<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
> [<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
> [<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
> [<c04dbd59>] do_last+0x186/0x49f
> [<c04dc415>] do_filp_open+0x1bd/0x459
> [<c045b191>] ? timekeeping_get_ns+0x16/0x54
> [<c05a9170>] ? might_fault+0x1e/0x20
> [<c04e479a>] ? alloc_fd+0x58/0xbe
> [<c04d1941>] do_sys_open+0x4d/0xe4
> [<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
> [<c04d1a24>] sys_open+0x23/0x2b
> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>
> You've got a gvfs (gnome-vfs?) process stuck waiting on a buffer
> lock. The onyl way I can see it getting stuck here is if it the
> buffer has not been unlocked somewhere. It's possible that it is
> stuck on the same buffer that the corruption error came from,
> but the corrupted buffer is unlocked in the error handling path.
> what does `xfs_repair -n` tell about the filesytsem?
>
> FWIW, later on:
>
> ......
> INFO: task gvfsd-trash:1891 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> gvfsd-trash D 00000026 0 1891 1 0x00000080
>
> gvfs-trashd gets stuck on a mutex during a path walk which is
> probably held by the above directory read.
>
> ....
> INFO: task gvfs-gdu-volume:2321 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> gvfs-gdu-volu D 00000026 0 2321 1 0x00000088
>
> As does this one.
>
> ....
>
> gvfs-gdu-volu D 00000026 0 1889 1 0x00000080
> cda3df10 00000086 a422923c 00000026 c0a25e00 c0a25e00 c0a25e00 c0a25e00
> cd936904 c0a25e00 c0a25e00 000b9ea1 00000000 cda24400 00000026 cd936680
> 00ae3000 c34c01a4 c34c019c cd936680 c34c01a0 cda3df44 c0782093 c34c01ac
> Call Trace:
> [<c0782093>] __mutex_lock_common+0xe8/0x137
> [<c0782113>] __mutex_lock_killable_slowpath+0x17/0x19
> [<c0782160>] ? mutex_lock_killable+0x32/0x45
> [<c0782160>] mutex_lock_killable+0x32/0x45
> [<c04deb0a>] vfs_readdir+0x46/0x94
> [<c04de814>] ? filldir64+0x0/0xf5
> [<c04debca>] sys_getdents64+0x72/0xb2
> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>
> And this one, too.
>
> .....
> ls D 00000000 0 2325 2044 0x00000080
> c6d03f10 00200086 00000000 00000000 c0a25e00 c0a25e00 c0a25e00 c0a25e00
> cdacb5c4 c0a25e00 c0a25e00 d6779fa1 00000029 00000000 00000029 cdacb340
> 00000001 c34c01a4 c34c019c cdacb340 c34c01a0 c6d03f44 c0782093 c34c01ac
> Call Trace:
> [<c0782093>] __mutex_lock_common+0xe8/0x137
> [<c0782113>] __mutex_lock_killable_slowpath+0x17/0x19
> [<c0782160>] ? mutex_lock_killable+0x32/0x45
> [<c0782160>] mutex_lock_killable+0x32/0x45
> [<c04deb0a>] vfs_readdir+0x46/0x94
> [<c04de814>] ? filldir64+0x0/0xf5
> [<c04debca>] sys_getdents64+0x72/0xb2
> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>
> And finally, there is an ls process that is hung, stuck on a
> directory mutex. Is this the one you were seeing hang rather than
> whatever generated the corrupion report?
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
[-- Attachment #2: xfs_repair_log --]
[-- Type: application/octet-stream, Size: 71732 bytes --]
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- scan filesystem freespace and inode maps...
sb_icount 64, counted 256
sb_ifree 56, counted 49
sb_fdblocks 1418987, counted 1425241
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
bad dir magic number 0xd2f1 in inode 128 bno = 8388608
data fork in ino 2319 claims free block 163
imap claims in-use inode 2319 is free, would correct imap
data fork in ino 2320 claims free block 164
imap claims in-use inode 2320 is free, would correct imap
imap claims in-use inode 2321 is free, would correct imap
imap claims in-use inode 2322 is free, would correct imap
imap claims in-use inode 2323 is free, would correct imap
imap claims in-use inode 2324 is free, would correct imap
imap claims in-use inode 2325 is free, would correct imap
imap claims in-use inode 2326 is free, would correct imap
imap claims in-use inode 2327 is free, would correct imap
imap claims in-use inode 2328 is free, would correct imap
imap claims in-use inode 2329 is free, would correct imap
imap claims in-use inode 2330 is free, would correct imap
imap claims in-use inode 2331 is free, would correct imap
imap claims in-use inode 2332 is free, would correct imap
imap claims in-use inode 2333 is free, would correct imap
imap claims in-use inode 2334 is free, would correct imap
imap claims in-use inode 2335 is free, would correct imap
imap claims in-use inode 2336 is free, would correct imap
imap claims in-use inode 2337 is free, would correct imap
imap claims in-use inode 2338 is free, would correct imap
imap claims in-use inode 2339 is free, would correct imap
imap claims in-use inode 2340 is free, would correct imap
imap claims in-use inode 2341 is free, would correct imap
imap claims in-use inode 2342 is free, would correct imap
imap claims in-use inode 2343 is free, would correct imap
imap claims in-use inode 2344 is free, would correct imap
imap claims in-use inode 2345 is free, would correct imap
imap claims in-use inode 2346 is free, would correct imap
imap claims in-use inode 2347 is free, would correct imap
imap claims in-use inode 2348 is free, would correct imap
imap claims in-use inode 2349 is free, would correct imap
imap claims in-use inode 2350 is free, would correct imap
imap claims in-use inode 2351 is free, would correct imap
imap claims in-use inode 2352 is free, would correct imap
imap claims in-use inode 2353 is free, would correct imap
imap claims in-use inode 2354 is free, would correct imap
imap claims in-use inode 2355 is free, would correct imap
imap claims in-use inode 2356 is free, would correct imap
imap claims in-use inode 2357 is free, would correct imap
imap claims in-use inode 2358 is free, would correct imap
imap claims in-use inode 2359 is free, would correct imap
imap claims in-use inode 2360 is free, would correct imap
imap claims in-use inode 2361 is free, would correct imap
imap claims in-use inode 2362 is free, would correct imap
imap claims in-use inode 2363 is free, would correct imap
imap claims in-use inode 2364 is free, would correct imap
imap claims in-use inode 2365 is free, would correct imap
imap claims in-use inode 2366 is free, would correct imap
imap claims in-use inode 2367 is free, would correct imap
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
b7f0f6c0: Badness in key lookup (length)
bp=(bno 5040, len 8192 bytes) key=(bno 5040, len 4096 bytes)
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 1
- agno = 3
- agno = 2
- agno = 0
entry "339.test" at block 2 offset 16 in directory inode 128 references non-existent inode 4501
would clear inode number in entry at offset 16...
entry "340.test" at block 2 offset 40 in directory inode 128 references non-existent inode 4502
would clear inode number in entry at offset 40...
entry "341.test" at block 2 offset 64 in directory inode 128 references non-existent inode 4503
would clear inode number in entry at offset 64...
entry "342.test" at block 2 offset 88 in directory inode 128 references non-existent inode 4504
would clear inode number in entry at offset 88...
entry "343.test" at block 2 offset 112 in directory inode 128 references non-existent inode 4505
would clear inode number in entry at offset 112...
entry "344.test" at block 2 offset 136 in directory inode 128 references non-existent inode 4506
would clear inode number in entry at offset 136...
entry "345.test" at block 2 offset 160 in directory inode 128 references non-existent inode 4507
would clear inode number in entry at offset 160...
entry "346.test" at block 2 offset 184 in directory inode 128 references non-existent inode 4508
would clear inode number in entry at offset 184...
entry "347.test" at block 2 offset 208 in directory inode 128 references non-existent inode 4509
would clear inode number in entry at offset 208...
entry "348.test" at block 2 offset 232 in directory inode 128 references non-existent inode 4510
would clear inode number in entry at offset 232...
entry "349.test" at block 2 offset 256 in directory inode 128 references non-existent inode 4511
would clear inode number in entry at offset 256...
entry "350.test" at block 2 offset 280 in directory inode 128 references non-existent inode 4512
would clear inode number in entry at offset 280...
entry "351.test" at block 2 offset 304 in directory inode 128 references non-existent inode 4513
would clear inode number in entry at offset 304...
entry "352.test" at block 2 offset 328 in directory inode 128 references non-existent inode 4514
would clear inode number in entry at offset 328...
entry "353.test" at block 2 offset 352 in directory inode 128 references non-existent inode 4515
would clear inode number in entry at offset 352...
entry "354.test" at block 2 offset 376 in directory inode 128 references non-existent inode 4516
would clear inode number in entry at offset 376...
entry "355.test" at block 2 offset 400 in directory inode 128 references non-existent inode 4517
would clear inode number in entry at offset 400...
entry "356.test" at block 2 offset 424 in directory inode 128 references non-existent inode 4518
would clear inode number in entry at offset 424...
entry "357.test" at block 2 offset 448 in directory inode 128 references non-existent inode 4519
would clear inode number in entry at offset 448...
entry "358.test" at block 2 offset 472 in directory inode 128 references non-existent inode 4520
would clear inode number in entry at offset 472...
entry "359.test" at block 2 offset 496 in directory inode 128 references non-existent inode 4521
would clear inode number in entry at offset 496...
entry "360.test" at block 2 offset 520 in directory inode 128 references non-existent inode 4522
would clear inode number in entry at offset 520...
entry "361.test" at block 2 offset 544 in directory inode 128 references non-existent inode 4523
would clear inode number in entry at offset 544...
entry "362.test" at block 2 offset 568 in directory inode 128 references non-existent inode 4524
would clear inode number in entry at offset 568...
entry "363.test" at block 2 offset 592 in directory inode 128 references non-existent inode 4525
would clear inode number in entry at offset 592...
entry "364.test" at block 2 offset 616 in directory inode 128 references non-existent inode 4526
would clear inode number in entry at offset 616...
entry "365.test" at block 2 offset 640 in directory inode 128 references non-existent inode 4527
would clear inode number in entry at offset 640...
entry "366.test" at block 2 offset 664 in directory inode 128 references non-existent inode 4528
would clear inode number in entry at offset 664...
entry "367.test" at block 2 offset 688 in directory inode 128 references non-existent inode 4529
would clear inode number in entry at offset 688...
entry "368.test" at block 2 offset 712 in directory inode 128 references non-existent inode 4530
would clear inode number in entry at offset 712...
entry "369.test" at block 2 offset 736 in directory inode 128 references non-existent inode 4531
would clear inode number in entry at offset 736...
entry "370.test" at block 2 offset 760 in directory inode 128 references non-existent inode 4532
would clear inode number in entry at offset 760...
entry "371.test" at block 2 offset 784 in directory inode 128 references non-existent inode 4533
would clear inode number in entry at offset 784...
entry "372.test" at block 2 offset 808 in directory inode 128 references non-existent inode 4534
would clear inode number in entry at offset 808...
entry "373.test" at block 2 offset 832 in directory inode 128 references non-existent inode 4535
would clear inode number in entry at offset 832...
entry "374.test" at block 2 offset 856 in directory inode 128 references non-existent inode 4536
would clear inode number in entry at offset 856...
entry "375.test" at block 2 offset 880 in directory inode 128 references non-existent inode 4537
would clear inode number in entry at offset 880...
entry "376.test" at block 2 offset 904 in directory inode 128 references non-existent inode 4538
would clear inode number in entry at offset 904...
entry "377.test" at block 2 offset 928 in directory inode 128 references non-existent inode 4539
would clear inode number in entry at offset 928...
entry "378.test" at block 2 offset 952 in directory inode 128 references non-existent inode 4540
would clear inode number in entry at offset 952...
entry "379.test" at block 2 offset 976 in directory inode 128 references non-existent inode 4541
would clear inode number in entry at offset 976...
entry "380.test" at block 2 offset 1000 in directory inode 128 references non-existent inode 4542
would clear inode number in entry at offset 1000...
entry "381.test" at block 2 offset 1024 in directory inode 128 references non-existent inode 4543
would clear inode number in entry at offset 1024...
entry "382.test" at block 2 offset 1048 in directory inode 128 references non-existent inode 5600
would clear inode number in entry at offset 1048...
entry "383.test" at block 2 offset 1072 in directory inode 128 references non-existent inode 5601
would clear inode number in entry at offset 1072...
entry "384.test" at block 2 offset 1096 in directory inode 128 references non-existent inode 5602
would clear inode number in entry at offset 1096...
entry "385.test" at block 2 offset 1120 in directory inode 128 references non-existent inode 5603
would clear inode number in entry at offset 1120...
entry "386.test" at block 2 offset 1144 in directory inode 128 references non-existent inode 5604
would clear inode number in entry at offset 1144...
entry "387.test" at block 2 offset 1168 in directory inode 128 references non-existent inode 5605
would clear inode number in entry at offset 1168...
entry "388.test" at block 2 offset 1192 in directory inode 128 references non-existent inode 5606
would clear inode number in entry at offset 1192...
entry "389.test" at block 2 offset 1216 in directory inode 128 references non-existent inode 5607
would clear inode number in entry at offset 1216...
entry "390.test" at block 2 offset 1240 in directory inode 128 references non-existent inode 5608
would clear inode number in entry at offset 1240...
entry "391.test" at block 2 offset 1264 in directory inode 128 references non-existent inode 5609
would clear inode number in entry at offset 1264...
entry "392.test" at block 2 offset 1288 in directory inode 128 references non-existent inode 5610
would clear inode number in entry at offset 1288...
entry "393.test" at block 2 offset 1312 in directory inode 128 references non-existent inode 5611
would clear inode number in entry at offset 1312...
entry "394.test" at block 2 offset 1336 in directory inode 128 references non-existent inode 5612
would clear inode number in entry at offset 1336...
entry "395.test" at block 2 offset 1360 in directory inode 128 references non-existent inode 5613
would clear inode number in entry at offset 1360...
entry "396.test" at block 2 offset 1384 in directory inode 128 references non-existent inode 5614
would clear inode number in entry at offset 1384...
entry "397.test" at block 2 offset 1408 in directory inode 128 references non-existent inode 5615
would clear inode number in entry at offset 1408...
entry "398.test" at block 2 offset 1432 in directory inode 128 references non-existent inode 5616
would clear inode number in entry at offset 1432...
entry "399.test" at block 2 offset 1456 in directory inode 128 references non-existent inode 5617
would clear inode number in entry at offset 1456...
entry "400.test" at block 2 offset 1480 in directory inode 128 references non-existent inode 5618
would clear inode number in entry at offset 1480...
entry "401.test" at block 2 offset 1504 in directory inode 128 references non-existent inode 5619
would clear inode number in entry at offset 1504...
entry "402.test" at block 2 offset 1528 in directory inode 128 references non-existent inode 5620
would clear inode number in entry at offset 1528...
entry "403.test" at block 2 offset 1552 in directory inode 128 references non-existent inode 5621
would clear inode number in entry at offset 1552...
entry "404.test" at block 2 offset 1576 in directory inode 128 references non-existent inode 5622
would clear inode number in entry at offset 1576...
entry "405.test" at block 2 offset 1600 in directory inode 128 references non-existent inode 5623
would clear inode number in entry at offset 1600...
entry "406.test" at block 2 offset 1624 in directory inode 128 references non-existent inode 5624
would clear inode number in entry at offset 1624...
entry "407.test" at block 2 offset 1648 in directory inode 128 references non-existent inode 5625
would clear inode number in entry at offset 1648...
entry "408.test" at block 2 offset 1672 in directory inode 128 references non-existent inode 5626
would clear inode number in entry at offset 1672...
entry "409.test" at block 2 offset 1696 in directory inode 128 references non-existent inode 5627
would clear inode number in entry at offset 1696...
entry "410.test" at block 2 offset 1720 in directory inode 128 references non-existent inode 5628
would clear inode number in entry at offset 1720...
entry "411.test" at block 2 offset 1744 in directory inode 128 references non-existent inode 5629
would clear inode number in entry at offset 1744...
entry "412.test" at block 2 offset 1768 in directory inode 128 references non-existent inode 5630
would clear inode number in entry at offset 1768...
entry "413.test" at block 2 offset 1792 in directory inode 128 references non-existent inode 5631
would clear inode number in entry at offset 1792...
entry "414.test" at block 2 offset 1816 in directory inode 128 references non-existent inode 5632
would clear inode number in entry at offset 1816...
entry "415.test" at block 2 offset 1840 in directory inode 128 references non-existent inode 5633
would clear inode number in entry at offset 1840...
entry "416.test" at block 2 offset 1864 in directory inode 128 references non-existent inode 5634
would clear inode number in entry at offset 1864...
entry "417.test" at block 2 offset 1888 in directory inode 128 references non-existent inode 5635
would clear inode number in entry at offset 1888...
entry "418.test" at block 2 offset 1912 in directory inode 128 references non-existent inode 5636
would clear inode number in entry at offset 1912...
entry "419.test" at block 2 offset 1936 in directory inode 128 references non-existent inode 5637
would clear inode number in entry at offset 1936...
entry "420.test" at block 2 offset 1960 in directory inode 128 references non-existent inode 5638
would clear inode number in entry at offset 1960...
entry "421.test" at block 2 offset 1984 in directory inode 128 references non-existent inode 5639
would clear inode number in entry at offset 1984...
entry "422.test" at block 2 offset 2008 in directory inode 128 references non-existent inode 5640
would clear inode number in entry at offset 2008...
entry "423.test" at block 2 offset 2032 in directory inode 128 references non-existent inode 5641
would clear inode number in entry at offset 2032...
entry "424.test" at block 2 offset 2056 in directory inode 128 references non-existent inode 5642
would clear inode number in entry at offset 2056...
entry "425.test" at block 2 offset 2080 in directory inode 128 references non-existent inode 5643
would clear inode number in entry at offset 2080...
entry "426.test" at block 2 offset 2104 in directory inode 128 references non-existent inode 5644
would clear inode number in entry at offset 2104...
entry "427.test" at block 2 offset 2128 in directory inode 128 references non-existent inode 5645
would clear inode number in entry at offset 2128...
entry "428.test" at block 2 offset 2152 in directory inode 128 references non-existent inode 5646
would clear inode number in entry at offset 2152...
entry "429.test" at block 2 offset 2176 in directory inode 128 references non-existent inode 5647
would clear inode number in entry at offset 2176...
entry "430.test" at block 2 offset 2200 in directory inode 128 references non-existent inode 5648
would clear inode number in entry at offset 2200...
entry "431.test" at block 2 offset 2224 in directory inode 128 references non-existent inode 5649
would clear inode number in entry at offset 2224...
entry "432.test" at block 2 offset 2248 in directory inode 128 references non-existent inode 5650
would clear inode number in entry at offset 2248...
entry "433.test" at block 2 offset 2272 in directory inode 128 references non-existent inode 5651
would clear inode number in entry at offset 2272...
entry "434.test" at block 2 offset 2296 in directory inode 128 references non-existent inode 5652
would clear inode number in entry at offset 2296...
entry "435.test" at block 2 offset 2320 in directory inode 128 references non-existent inode 5653
would clear inode number in entry at offset 2320...
entry "436.test" at block 2 offset 2344 in directory inode 128 references non-existent inode 5654
would clear inode number in entry at offset 2344...
entry "437.test" at block 2 offset 2368 in directory inode 128 references non-existent inode 5655
would clear inode number in entry at offset 2368...
entry "438.test" at block 2 offset 2392 in directory inode 128 references non-existent inode 5656
would clear inode number in entry at offset 2392...
entry "439.test" at block 2 offset 2416 in directory inode 128 references non-existent inode 5657
would clear inode number in entry at offset 2416...
entry "440.test" at block 2 offset 2440 in directory inode 128 references non-existent inode 5658
would clear inode number in entry at offset 2440...
entry "441.test" at block 2 offset 2464 in directory inode 128 references non-existent inode 5659
would clear inode number in entry at offset 2464...
entry "442.test" at block 2 offset 2488 in directory inode 128 references non-existent inode 5660
would clear inode number in entry at offset 2488...
entry "443.test" at block 2 offset 2512 in directory inode 128 references non-existent inode 5661
would clear inode number in entry at offset 2512...
entry "444.test" at block 2 offset 2536 in directory inode 128 references non-existent inode 5662
would clear inode number in entry at offset 2536...
entry "445.test" at block 2 offset 2560 in directory inode 128 references non-existent inode 5663
would clear inode number in entry at offset 2560...
entry "446.test" at block 2 offset 2584 in directory inode 128 references non-existent inode 6688
would clear inode number in entry at offset 2584...
entry "447.test" at block 2 offset 2608 in directory inode 128 references non-existent inode 6689
would clear inode number in entry at offset 2608...
entry "448.test" at block 2 offset 2632 in directory inode 128 references non-existent inode 6690
would clear inode number in entry at offset 2632...
entry "449.test" at block 2 offset 2656 in directory inode 128 references non-existent inode 6691
would clear inode number in entry at offset 2656...
entry "450.test" at block 2 offset 2680 in directory inode 128 references non-existent inode 6692
would clear inode number in entry at offset 2680...
entry "451.test" at block 2 offset 2704 in directory inode 128 references non-existent inode 6693
would clear inode number in entry at offset 2704...
entry "452.test" at block 2 offset 2728 in directory inode 128 references non-existent inode 6694
would clear inode number in entry at offset 2728...
entry "453.test" at block 2 offset 2752 in directory inode 128 references non-existent inode 6695
would clear inode number in entry at offset 2752...
entry "454.test" at block 2 offset 2776 in directory inode 128 references non-existent inode 6696
would clear inode number in entry at offset 2776...
entry "455.test" at block 2 offset 2800 in directory inode 128 references non-existent inode 6697
would clear inode number in entry at offset 2800...
entry "456.test" at block 2 offset 2824 in directory inode 128 references non-existent inode 6698
would clear inode number in entry at offset 2824...
entry "457.test" at block 2 offset 2848 in directory inode 128 references non-existent inode 6699
would clear inode number in entry at offset 2848...
entry "458.test" at block 2 offset 2872 in directory inode 128 references non-existent inode 6700
would clear inode number in entry at offset 2872...
entry "459.test" at block 2 offset 2896 in directory inode 128 references non-existent inode 6701
would clear inode number in entry at offset 2896...
entry "460.test" at block 2 offset 2920 in directory inode 128 references non-existent inode 6702
would clear inode number in entry at offset 2920...
entry "461.test" at block 2 offset 2944 in directory inode 128 references non-existent inode 6703
would clear inode number in entry at offset 2944...
entry "462.test" at block 2 offset 2968 in directory inode 128 references non-existent inode 6704
would clear inode number in entry at offset 2968...
entry "463.test" at block 2 offset 2992 in directory inode 128 references non-existent inode 6705
would clear inode number in entry at offset 2992...
entry "464.test" at block 2 offset 3016 in directory inode 128 references non-existent inode 6706
would clear inode number in entry at offset 3016...
entry "465.test" at block 2 offset 3040 in directory inode 128 references non-existent inode 6707
would clear inode number in entry at offset 3040...
entry "466.test" at block 2 offset 3064 in directory inode 128 references non-existent inode 6708
would clear inode number in entry at offset 3064...
entry "467.test" at block 2 offset 3088 in directory inode 128 references non-existent inode 6709
would clear inode number in entry at offset 3088...
entry "468.test" at block 2 offset 3112 in directory inode 128 references non-existent inode 6710
would clear inode number in entry at offset 3112...
entry "469.test" at block 2 offset 3136 in directory inode 128 references non-existent inode 6711
would clear inode number in entry at offset 3136...
entry "470.test" at block 2 offset 3160 in directory inode 128 references non-existent inode 6712
would clear inode number in entry at offset 3160...
entry "471.test" at block 2 offset 3184 in directory inode 128 references non-existent inode 6713
would clear inode number in entry at offset 3184...
entry "472.test" at block 2 offset 3208 in directory inode 128 references non-existent inode 6714
would clear inode number in entry at offset 3208...
entry "473.test" at block 2 offset 3232 in directory inode 128 references non-existent inode 6715
would clear inode number in entry at offset 3232...
entry "474.test" at block 2 offset 3256 in directory inode 128 references non-existent inode 6716
would clear inode number in entry at offset 3256...
entry "475.test" at block 2 offset 3280 in directory inode 128 references non-existent inode 6717
would clear inode number in entry at offset 3280...
entry "476.test" at block 2 offset 3304 in directory inode 128 references non-existent inode 6718
would clear inode number in entry at offset 3304...
entry "477.test" at block 2 offset 3328 in directory inode 128 references non-existent inode 6719
would clear inode number in entry at offset 3328...
entry "478.test" at block 2 offset 3352 in directory inode 128 references non-existent inode 6720
would clear inode number in entry at offset 3352...
entry "479.test" at block 2 offset 3376 in directory inode 128 references non-existent inode 6721
would clear inode number in entry at offset 3376...
entry "480.test" at block 2 offset 3400 in directory inode 128 references non-existent inode 6722
would clear inode number in entry at offset 3400...
entry "481.test" at block 2 offset 3424 in directory inode 128 references non-existent inode 6723
would clear inode number in entry at offset 3424...
entry "482.test" at block 2 offset 3448 in directory inode 128 references non-existent inode 6724
would clear inode number in entry at offset 3448...
entry "483.test" at block 2 offset 3472 in directory inode 128 references non-existent inode 6725
would clear inode number in entry at offset 3472...
entry "484.test" at block 2 offset 3496 in directory inode 128 references non-existent inode 6726
would clear inode number in entry at offset 3496...
entry "485.test" at block 2 offset 3520 in directory inode 128 references non-existent inode 6727
would clear inode number in entry at offset 3520...
entry "486.test" at block 2 offset 3544 in directory inode 128 references non-existent inode 6728
would clear inode number in entry at offset 3544...
entry "487.test" at block 2 offset 3568 in directory inode 128 references non-existent inode 6729
would clear inode number in entry at offset 3568...
entry "488.test" at block 2 offset 3592 in directory inode 128 references non-existent inode 6730
would clear inode number in entry at offset 3592...
entry "489.test" at block 2 offset 3616 in directory inode 128 references non-existent inode 6731
would clear inode number in entry at offset 3616...
entry "490.test" at block 2 offset 3640 in directory inode 128 references non-existent inode 6732
would clear inode number in entry at offset 3640...
entry "491.test" at block 2 offset 3664 in directory inode 128 references non-existent inode 6733
would clear inode number in entry at offset 3664...
entry "492.test" at block 2 offset 3688 in directory inode 128 references non-existent inode 6734
would clear inode number in entry at offset 3688...
entry "493.test" at block 2 offset 3712 in directory inode 128 references non-existent inode 6735
would clear inode number in entry at offset 3712...
entry "494.test" at block 2 offset 3736 in directory inode 128 references non-existent inode 6736
would clear inode number in entry at offset 3736...
entry "495.test" at block 2 offset 3760 in directory inode 128 references non-existent inode 6737
would clear inode number in entry at offset 3760...
entry "496.test" at block 2 offset 3784 in directory inode 128 references non-existent inode 6738
would clear inode number in entry at offset 3784...
entry "497.test" at block 2 offset 3808 in directory inode 128 references non-existent inode 6739
would clear inode number in entry at offset 3808...
entry "498.test" at block 2 offset 3832 in directory inode 128 references non-existent inode 6740
would clear inode number in entry at offset 3832...
entry "499.test" at block 2 offset 3856 in directory inode 128 references non-existent inode 6741
would clear inode number in entry at offset 3856...
entry "500.test" at block 2 offset 3880 in directory inode 128 references non-existent inode 6742
would clear inode number in entry at offset 3880...
entry "501.test" at block 2 offset 3904 in directory inode 128 references non-existent inode 6743
would clear inode number in entry at offset 3904...
entry "502.test" at block 2 offset 3928 in directory inode 128 references non-existent inode 6744
would clear inode number in entry at offset 3928...
entry "503.test" at block 2 offset 3952 in directory inode 128 references non-existent inode 6745
would clear inode number in entry at offset 3952...
entry "504.test" at block 2 offset 3976 in directory inode 128 references non-existent inode 6746
would clear inode number in entry at offset 3976...
entry "505.test" at block 2 offset 4000 in directory inode 128 references non-existent inode 6747
would clear inode number in entry at offset 4000...
entry "506.test" at block 2 offset 4024 in directory inode 128 references non-existent inode 6748
would clear inode number in entry at offset 4024...
entry "507.test" at block 2 offset 4048 in directory inode 128 references non-existent inode 6749
would clear inode number in entry at offset 4048...
entry "508.test" at block 2 offset 4072 in directory inode 128 references non-existent inode 6750
would clear inode number in entry at offset 4072...
entry "509.test" at block 3 offset 16 in directory inode 128 references non-existent inode 6751
would clear inode number in entry at offset 16...
entry "510.test" at block 3 offset 40 in directory inode 128 references non-existent inode 7840
would clear inode number in entry at offset 40...
entry "511.test" at block 3 offset 64 in directory inode 128 references non-existent inode 7841
would clear inode number in entry at offset 64...
entry "512.test" at block 3 offset 88 in directory inode 128 references non-existent inode 7842
would clear inode number in entry at offset 88...
entry "513.test" at block 3 offset 112 in directory inode 128 references non-existent inode 7843
would clear inode number in entry at offset 112...
entry "514.test" at block 3 offset 136 in directory inode 128 references non-existent inode 7844
would clear inode number in entry at offset 136...
entry "515.test" at block 3 offset 160 in directory inode 128 references non-existent inode 7845
would clear inode number in entry at offset 160...
entry "516.test" at block 3 offset 184 in directory inode 128 references non-existent inode 7846
would clear inode number in entry at offset 184...
entry "517.test" at block 3 offset 208 in directory inode 128 references non-existent inode 7847
would clear inode number in entry at offset 208...
entry "518.test" at block 3 offset 232 in directory inode 128 references non-existent inode 7848
would clear inode number in entry at offset 232...
entry "519.test" at block 3 offset 256 in directory inode 128 references non-existent inode 7849
would clear inode number in entry at offset 256...
entry "520.test" at block 3 offset 280 in directory inode 128 references non-existent inode 7850
would clear inode number in entry at offset 280...
entry "521.test" at block 3 offset 304 in directory inode 128 references non-existent inode 7851
would clear inode number in entry at offset 304...
entry "522.test" at block 3 offset 328 in directory inode 128 references non-existent inode 7852
would clear inode number in entry at offset 328...
entry "523.test" at block 3 offset 352 in directory inode 128 references non-existent inode 7853
would clear inode number in entry at offset 352...
entry "524.test" at block 3 offset 376 in directory inode 128 references non-existent inode 7854
would clear inode number in entry at offset 376...
entry "525.test" at block 3 offset 400 in directory inode 128 references non-existent inode 7855
would clear inode number in entry at offset 400...
entry "526.test" at block 3 offset 424 in directory inode 128 references non-existent inode 7856
would clear inode number in entry at offset 424...
entry "527.test" at block 3 offset 448 in directory inode 128 references non-existent inode 7857
would clear inode number in entry at offset 448...
entry "528.test" at block 3 offset 472 in directory inode 128 references non-existent inode 7858
would clear inode number in entry at offset 472...
entry "529.test" at block 3 offset 496 in directory inode 128 references non-existent inode 7859
would clear inode number in entry at offset 496...
entry "530.test" at block 3 offset 520 in directory inode 128 references non-existent inode 7860
would clear inode number in entry at offset 520...
entry "531.test" at block 3 offset 544 in directory inode 128 references non-existent inode 7861
would clear inode number in entry at offset 544...
entry "532.test" at block 3 offset 568 in directory inode 128 references non-existent inode 7862
would clear inode number in entry at offset 568...
entry "533.test" at block 3 offset 592 in directory inode 128 references non-existent inode 7863
would clear inode number in entry at offset 592...
entry "534.test" at block 3 offset 616 in directory inode 128 references non-existent inode 7864
would clear inode number in entry at offset 616...
entry "535.test" at block 3 offset 640 in directory inode 128 references non-existent inode 7865
would clear inode number in entry at offset 640...
entry "536.test" at block 3 offset 664 in directory inode 128 references non-existent inode 7866
would clear inode number in entry at offset 664...
entry "537.test" at block 3 offset 688 in directory inode 128 references non-existent inode 7867
would clear inode number in entry at offset 688...
entry "538.test" at block 3 offset 712 in directory inode 128 references non-existent inode 7868
would clear inode number in entry at offset 712...
entry "539.test" at block 3 offset 736 in directory inode 128 references non-existent inode 7869
would clear inode number in entry at offset 736...
entry "540.test" at block 3 offset 760 in directory inode 128 references non-existent inode 7870
would clear inode number in entry at offset 760...
entry "541.test" at block 3 offset 784 in directory inode 128 references non-existent inode 7871
would clear inode number in entry at offset 784...
entry "542.test" at block 3 offset 808 in directory inode 128 references non-existent inode 7872
would clear inode number in entry at offset 808...
entry "543.test" at block 3 offset 832 in directory inode 128 references non-existent inode 7873
would clear inode number in entry at offset 832...
entry "544.test" at block 3 offset 856 in directory inode 128 references non-existent inode 7874
would clear inode number in entry at offset 856...
entry "545.test" at block 3 offset 880 in directory inode 128 references non-existent inode 7875
would clear inode number in entry at offset 880...
entry "546.test" at block 3 offset 904 in directory inode 128 references non-existent inode 7876
would clear inode number in entry at offset 904...
entry "547.test" at block 3 offset 928 in directory inode 128 references non-existent inode 7877
would clear inode number in entry at offset 928...
entry "548.test" at block 3 offset 952 in directory inode 128 references non-existent inode 7878
would clear inode number in entry at offset 952...
entry "549.test" at block 3 offset 976 in directory inode 128 references non-existent inode 7879
would clear inode number in entry at offset 976...
entry "550.test" at block 3 offset 1000 in directory inode 128 references non-existent inode 7880
would clear inode number in entry at offset 1000...
entry "551.test" at block 3 offset 1024 in directory inode 128 references non-existent inode 7881
would clear inode number in entry at offset 1024...
entry "552.test" at block 3 offset 1048 in directory inode 128 references non-existent inode 7882
would clear inode number in entry at offset 1048...
entry "553.test" at block 3 offset 1072 in directory inode 128 references non-existent inode 7883
would clear inode number in entry at offset 1072...
entry "554.test" at block 3 offset 1096 in directory inode 128 references non-existent inode 7884
would clear inode number in entry at offset 1096...
entry "555.test" at block 3 offset 1120 in directory inode 128 references non-existent inode 7885
would clear inode number in entry at offset 1120...
entry "556.test" at block 3 offset 1144 in directory inode 128 references non-existent inode 7886
would clear inode number in entry at offset 1144...
entry "557.test" at block 3 offset 1168 in directory inode 128 references non-existent inode 7887
would clear inode number in entry at offset 1168...
entry "558.test" at block 3 offset 1192 in directory inode 128 references non-existent inode 7888
would clear inode number in entry at offset 1192...
entry "559.test" at block 3 offset 1216 in directory inode 128 references non-existent inode 7889
would clear inode number in entry at offset 1216...
entry "560.test" at block 3 offset 1240 in directory inode 128 references non-existent inode 7890
would clear inode number in entry at offset 1240...
entry "561.test" at block 3 offset 1264 in directory inode 128 references non-existent inode 7891
would clear inode number in entry at offset 1264...
entry "562.test" at block 3 offset 1288 in directory inode 128 references non-existent inode 7892
would clear inode number in entry at offset 1288...
entry "563.test" at block 3 offset 1312 in directory inode 128 references non-existent inode 7893
would clear inode number in entry at offset 1312...
entry "564.test" at block 3 offset 1336 in directory inode 128 references non-existent inode 7894
would clear inode number in entry at offset 1336...
entry "565.test" at block 3 offset 1360 in directory inode 128 references non-existent inode 7895
would clear inode number in entry at offset 1360...
entry "566.test" at block 3 offset 1384 in directory inode 128 references non-existent inode 7896
would clear inode number in entry at offset 1384...
entry "567.test" at block 3 offset 1408 in directory inode 128 references non-existent inode 7897
would clear inode number in entry at offset 1408...
entry "568.test" at block 3 offset 1432 in directory inode 128 references non-existent inode 7898
would clear inode number in entry at offset 1432...
entry "569.test" at block 3 offset 1456 in directory inode 128 references non-existent inode 7899
would clear inode number in entry at offset 1456...
entry "570.test" at block 3 offset 1480 in directory inode 128 references non-existent inode 7900
would clear inode number in entry at offset 1480...
entry "571.test" at block 3 offset 1504 in directory inode 128 references non-existent inode 7901
would clear inode number in entry at offset 1504...
entry "572.test" at block 3 offset 1528 in directory inode 128 references non-existent inode 7902
would clear inode number in entry at offset 1528...
entry "573.test" at block 3 offset 1552 in directory inode 128 references non-existent inode 7903
would clear inode number in entry at offset 1552...
entry "574.test" at block 3 offset 1576 in directory inode 128 references non-existent inode 10016
would clear inode number in entry at offset 1576...
entry "575.test" at block 3 offset 1600 in directory inode 128 references non-existent inode 10017
would clear inode number in entry at offset 1600...
entry "576.test" at block 3 offset 1624 in directory inode 128 references non-existent inode 10018
would clear inode number in entry at offset 1624...
entry "577.test" at block 3 offset 1648 in directory inode 128 references non-existent inode 10019
would clear inode number in entry at offset 1648...
entry "578.test" at block 3 offset 1672 in directory inode 128 references non-existent inode 10020
would clear inode number in entry at offset 1672...
entry "579.test" at block 3 offset 1696 in directory inode 128 references non-existent inode 10021
would clear inode number in entry at offset 1696...
entry "580.test" at block 3 offset 1720 in directory inode 128 references non-existent inode 10022
would clear inode number in entry at offset 1720...
entry "581.test" at block 3 offset 1744 in directory inode 128 references non-existent inode 10023
would clear inode number in entry at offset 1744...
entry "582.test" at block 3 offset 1768 in directory inode 128 references non-existent inode 10024
would clear inode number in entry at offset 1768...
entry "583.test" at block 3 offset 1792 in directory inode 128 references non-existent inode 10025
would clear inode number in entry at offset 1792...
entry "584.test" at block 3 offset 1816 in directory inode 128 references non-existent inode 10026
would clear inode number in entry at offset 1816...
entry "585.test" at block 3 offset 1840 in directory inode 128 references non-existent inode 10027
would clear inode number in entry at offset 1840...
entry "586.test" at block 3 offset 1864 in directory inode 128 references non-existent inode 10028
would clear inode number in entry at offset 1864...
entry "587.test" at block 3 offset 1888 in directory inode 128 references non-existent inode 10029
would clear inode number in entry at offset 1888...
entry "588.test" at block 3 offset 1912 in directory inode 128 references non-existent inode 10030
would clear inode number in entry at offset 1912...
entry "589.test" at block 3 offset 1936 in directory inode 128 references non-existent inode 10031
would clear inode number in entry at offset 1936...
entry "590.test" at block 3 offset 1960 in directory inode 128 references non-existent inode 10032
would clear inode number in entry at offset 1960...
entry "591.test" at block 3 offset 1984 in directory inode 128 references non-existent inode 10033
would clear inode number in entry at offset 1984...
entry "592.test" at block 3 offset 2008 in directory inode 128 references non-existent inode 10034
would clear inode number in entry at offset 2008...
entry "593.test" at block 3 offset 2032 in directory inode 128 references non-existent inode 10035
would clear inode number in entry at offset 2032...
entry "594.test" at block 3 offset 2056 in directory inode 128 references non-existent inode 10036
would clear inode number in entry at offset 2056...
entry "595.test" at block 3 offset 2080 in directory inode 128 references non-existent inode 10037
would clear inode number in entry at offset 2080...
entry "596.test" at block 3 offset 2104 in directory inode 128 references non-existent inode 10038
would clear inode number in entry at offset 2104...
entry "597.test" at block 3 offset 2128 in directory inode 128 references non-existent inode 10039
would clear inode number in entry at offset 2128...
entry "598.test" at block 3 offset 2152 in directory inode 128 references non-existent inode 10040
would clear inode number in entry at offset 2152...
entry "599.test" at block 3 offset 2176 in directory inode 128 references non-existent inode 10041
would clear inode number in entry at offset 2176...
entry "600.test" at block 3 offset 2200 in directory inode 128 references non-existent inode 10042
would clear inode number in entry at offset 2200...
entry "601.test" at block 3 offset 2224 in directory inode 128 references non-existent inode 10043
would clear inode number in entry at offset 2224...
entry "602.test" at block 3 offset 2248 in directory inode 128 references non-existent inode 10044
would clear inode number in entry at offset 2248...
entry "603.test" at block 3 offset 2272 in directory inode 128 references non-existent inode 10045
would clear inode number in entry at offset 2272...
entry "604.test" at block 3 offset 2296 in directory inode 128 references non-existent inode 10046
would clear inode number in entry at offset 2296...
entry "605.test" at block 3 offset 2320 in directory inode 128 references non-existent inode 10047
would clear inode number in entry at offset 2320...
entry "606.test" at block 3 offset 2344 in directory inode 128 references non-existent inode 10048
would clear inode number in entry at offset 2344...
b5055b90: Badness in key lookup (length)
bp=(bno 5040, len 4096 bytes) key=(bno 5040, len 8192 bytes)
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "339.test" in directory inode 128 points to non-existent inode 4501, would junk entry
entry "340.test" in directory inode 128 points to non-existent inode 4502, would junk entry
entry "341.test" in directory inode 128 points to non-existent inode 4503, would junk entry
entry "342.test" in directory inode 128 points to non-existent inode 4504, would junk entry
entry "343.test" in directory inode 128 points to non-existent inode 4505, would junk entry
entry "344.test" in directory inode 128 points to non-existent inode 4506, would junk entry
entry "345.test" in directory inode 128 points to non-existent inode 4507, would junk entry
entry "346.test" in directory inode 128 points to non-existent inode 4508, would junk entry
entry "347.test" in directory inode 128 points to non-existent inode 4509, would junk entry
entry "348.test" in directory inode 128 points to non-existent inode 4510, would junk entry
entry "349.test" in directory inode 128 points to non-existent inode 4511, would junk entry
entry "350.test" in directory inode 128 points to non-existent inode 4512, would junk entry
entry "351.test" in directory inode 128 points to non-existent inode 4513, would junk entry
entry "352.test" in directory inode 128 points to non-existent inode 4514, would junk entry
entry "353.test" in directory inode 128 points to non-existent inode 4515, would junk entry
entry "354.test" in directory inode 128 points to non-existent inode 4516, would junk entry
entry "355.test" in directory inode 128 points to non-existent inode 4517, would junk entry
entry "356.test" in directory inode 128 points to non-existent inode 4518, would junk entry
entry "357.test" in directory inode 128 points to non-existent inode 4519, would junk entry
entry "358.test" in directory inode 128 points to non-existent inode 4520, would junk entry
entry "359.test" in directory inode 128 points to non-existent inode 4521, would junk entry
entry "360.test" in directory inode 128 points to non-existent inode 4522, would junk entry
entry "361.test" in directory inode 128 points to non-existent inode 4523, would junk entry
entry "362.test" in directory inode 128 points to non-existent inode 4524, would junk entry
entry "363.test" in directory inode 128 points to non-existent inode 4525, would junk entry
entry "364.test" in directory inode 128 points to non-existent inode 4526, would junk entry
entry "365.test" in directory inode 128 points to non-existent inode 4527, would junk entry
entry "366.test" in directory inode 128 points to non-existent inode 4528, would junk entry
entry "367.test" in directory inode 128 points to non-existent inode 4529, would junk entry
entry "368.test" in directory inode 128 points to non-existent inode 4530, would junk entry
entry "369.test" in directory inode 128 points to non-existent inode 4531, would junk entry
entry "370.test" in directory inode 128 points to non-existent inode 4532, would junk entry
entry "371.test" in directory inode 128 points to non-existent inode 4533, would junk entry
entry "372.test" in directory inode 128 points to non-existent inode 4534, would junk entry
entry "373.test" in directory inode 128 points to non-existent inode 4535, would junk entry
entry "374.test" in directory inode 128 points to non-existent inode 4536, would junk entry
entry "375.test" in directory inode 128 points to non-existent inode 4537, would junk entry
entry "376.test" in directory inode 128 points to non-existent inode 4538, would junk entry
entry "377.test" in directory inode 128 points to non-existent inode 4539, would junk entry
entry "378.test" in directory inode 128 points to non-existent inode 4540, would junk entry
entry "379.test" in directory inode 128 points to non-existent inode 4541, would junk entry
entry "380.test" in directory inode 128 points to non-existent inode 4542, would junk entry
entry "381.test" in directory inode 128 points to non-existent inode 4543, would junk entry
entry "382.test" in directory inode 128 points to non-existent inode 5600, would junk entry
entry "383.test" in directory inode 128 points to non-existent inode 5601, would junk entry
entry "384.test" in directory inode 128 points to non-existent inode 5602, would junk entry
entry "385.test" in directory inode 128 points to non-existent inode 5603, would junk entry
entry "386.test" in directory inode 128 points to non-existent inode 5604, would junk entry
entry "387.test" in directory inode 128 points to non-existent inode 5605, would junk entry
entry "388.test" in directory inode 128 points to non-existent inode 5606, would junk entry
entry "389.test" in directory inode 128 points to non-existent inode 5607, would junk entry
entry "390.test" in directory inode 128 points to non-existent inode 5608, would junk entry
entry "391.test" in directory inode 128 points to non-existent inode 5609, would junk entry
entry "392.test" in directory inode 128 points to non-existent inode 5610, would junk entry
entry "393.test" in directory inode 128 points to non-existent inode 5611, would junk entry
entry "394.test" in directory inode 128 points to non-existent inode 5612, would junk entry
entry "395.test" in directory inode 128 points to non-existent inode 5613, would junk entry
entry "396.test" in directory inode 128 points to non-existent inode 5614, would junk entry
entry "397.test" in directory inode 128 points to non-existent inode 5615, would junk entry
entry "398.test" in directory inode 128 points to non-existent inode 5616, would junk entry
entry "399.test" in directory inode 128 points to non-existent inode 5617, would junk entry
entry "400.test" in directory inode 128 points to non-existent inode 5618, would junk entry
entry "401.test" in directory inode 128 points to non-existent inode 5619, would junk entry
entry "402.test" in directory inode 128 points to non-existent inode 5620, would junk entry
entry "403.test" in directory inode 128 points to non-existent inode 5621, would junk entry
entry "404.test" in directory inode 128 points to non-existent inode 5622, would junk entry
entry "405.test" in directory inode 128 points to non-existent inode 5623, would junk entry
entry "406.test" in directory inode 128 points to non-existent inode 5624, would junk entry
entry "407.test" in directory inode 128 points to non-existent inode 5625, would junk entry
entry "408.test" in directory inode 128 points to non-existent inode 5626, would junk entry
entry "409.test" in directory inode 128 points to non-existent inode 5627, would junk entry
entry "410.test" in directory inode 128 points to non-existent inode 5628, would junk entry
entry "411.test" in directory inode 128 points to non-existent inode 5629, would junk entry
entry "412.test" in directory inode 128 points to non-existent inode 5630, would junk entry
entry "413.test" in directory inode 128 points to non-existent inode 5631, would junk entry
entry "414.test" in directory inode 128 points to non-existent inode 5632, would junk entry
entry "415.test" in directory inode 128 points to non-existent inode 5633, would junk entry
entry "416.test" in directory inode 128 points to non-existent inode 5634, would junk entry
entry "417.test" in directory inode 128 points to non-existent inode 5635, would junk entry
entry "418.test" in directory inode 128 points to non-existent inode 5636, would junk entry
entry "419.test" in directory inode 128 points to non-existent inode 5637, would junk entry
entry "420.test" in directory inode 128 points to non-existent inode 5638, would junk entry
entry "421.test" in directory inode 128 points to non-existent inode 5639, would junk entry
entry "422.test" in directory inode 128 points to non-existent inode 5640, would junk entry
entry "423.test" in directory inode 128 points to non-existent inode 5641, would junk entry
entry "424.test" in directory inode 128 points to non-existent inode 5642, would junk entry
entry "425.test" in directory inode 128 points to non-existent inode 5643, would junk entry
entry "426.test" in directory inode 128 points to non-existent inode 5644, would junk entry
entry "427.test" in directory inode 128 points to non-existent inode 5645, would junk entry
entry "428.test" in directory inode 128 points to non-existent inode 5646, would junk entry
entry "429.test" in directory inode 128 points to non-existent inode 5647, would junk entry
entry "430.test" in directory inode 128 points to non-existent inode 5648, would junk entry
entry "431.test" in directory inode 128 points to non-existent inode 5649, would junk entry
entry "432.test" in directory inode 128 points to non-existent inode 5650, would junk entry
entry "433.test" in directory inode 128 points to non-existent inode 5651, would junk entry
entry "434.test" in directory inode 128 points to non-existent inode 5652, would junk entry
entry "435.test" in directory inode 128 points to non-existent inode 5653, would junk entry
entry "436.test" in directory inode 128 points to non-existent inode 5654, would junk entry
entry "437.test" in directory inode 128 points to non-existent inode 5655, would junk entry
entry "438.test" in directory inode 128 points to non-existent inode 5656, would junk entry
entry "439.test" in directory inode 128 points to non-existent inode 5657, would junk entry
entry "440.test" in directory inode 128 points to non-existent inode 5658, would junk entry
entry "441.test" in directory inode 128 points to non-existent inode 5659, would junk entry
entry "442.test" in directory inode 128 points to non-existent inode 5660, would junk entry
entry "443.test" in directory inode 128 points to non-existent inode 5661, would junk entry
entry "444.test" in directory inode 128 points to non-existent inode 5662, would junk entry
entry "445.test" in directory inode 128 points to non-existent inode 5663, would junk entry
entry "446.test" in directory inode 128 points to non-existent inode 6688, would junk entry
entry "447.test" in directory inode 128 points to non-existent inode 6689, would junk entry
entry "448.test" in directory inode 128 points to non-existent inode 6690, would junk entry
entry "449.test" in directory inode 128 points to non-existent inode 6691, would junk entry
entry "450.test" in directory inode 128 points to non-existent inode 6692, would junk entry
entry "451.test" in directory inode 128 points to non-existent inode 6693, would junk entry
entry "452.test" in directory inode 128 points to non-existent inode 6694, would junk entry
entry "453.test" in directory inode 128 points to non-existent inode 6695, would junk entry
entry "454.test" in directory inode 128 points to non-existent inode 6696, would junk entry
entry "455.test" in directory inode 128 points to non-existent inode 6697, would junk entry
entry "456.test" in directory inode 128 points to non-existent inode 6698, would junk entry
entry "457.test" in directory inode 128 points to non-existent inode 6699, would junk entry
entry "458.test" in directory inode 128 points to non-existent inode 6700, would junk entry
entry "459.test" in directory inode 128 points to non-existent inode 6701, would junk entry
entry "460.test" in directory inode 128 points to non-existent inode 6702, would junk entry
entry "461.test" in directory inode 128 points to non-existent inode 6703, would junk entry
entry "462.test" in directory inode 128 points to non-existent inode 6704, would junk entry
entry "463.test" in directory inode 128 points to non-existent inode 6705, would junk entry
entry "464.test" in directory inode 128 points to non-existent inode 6706, would junk entry
entry "465.test" in directory inode 128 points to non-existent inode 6707, would junk entry
entry "466.test" in directory inode 128 points to non-existent inode 6708, would junk entry
entry "467.test" in directory inode 128 points to non-existent inode 6709, would junk entry
entry "468.test" in directory inode 128 points to non-existent inode 6710, would junk entry
entry "469.test" in directory inode 128 points to non-existent inode 6711, would junk entry
entry "470.test" in directory inode 128 points to non-existent inode 6712, would junk entry
entry "471.test" in directory inode 128 points to non-existent inode 6713, would junk entry
entry "472.test" in directory inode 128 points to non-existent inode 6714, would junk entry
entry "473.test" in directory inode 128 points to non-existent inode 6715, would junk entry
entry "474.test" in directory inode 128 points to non-existent inode 6716, would junk entry
entry "475.test" in directory inode 128 points to non-existent inode 6717, would junk entry
entry "476.test" in directory inode 128 points to non-existent inode 6718, would junk entry
entry "477.test" in directory inode 128 points to non-existent inode 6719, would junk entry
entry "478.test" in directory inode 128 points to non-existent inode 6720, would junk entry
entry "479.test" in directory inode 128 points to non-existent inode 6721, would junk entry
entry "480.test" in directory inode 128 points to non-existent inode 6722, would junk entry
entry "481.test" in directory inode 128 points to non-existent inode 6723, would junk entry
entry "482.test" in directory inode 128 points to non-existent inode 6724, would junk entry
entry "483.test" in directory inode 128 points to non-existent inode 6725, would junk entry
entry "484.test" in directory inode 128 points to non-existent inode 6726, would junk entry
entry "485.test" in directory inode 128 points to non-existent inode 6727, would junk entry
entry "486.test" in directory inode 128 points to non-existent inode 6728, would junk entry
entry "487.test" in directory inode 128 points to non-existent inode 6729, would junk entry
entry "488.test" in directory inode 128 points to non-existent inode 6730, would junk entry
entry "489.test" in directory inode 128 points to non-existent inode 6731, would junk entry
entry "490.test" in directory inode 128 points to non-existent inode 6732, would junk entry
entry "491.test" in directory inode 128 points to non-existent inode 6733, would junk entry
entry "492.test" in directory inode 128 points to non-existent inode 6734, would junk entry
entry "493.test" in directory inode 128 points to non-existent inode 6735, would junk entry
entry "494.test" in directory inode 128 points to non-existent inode 6736, would junk entry
entry "495.test" in directory inode 128 points to non-existent inode 6737, would junk entry
entry "496.test" in directory inode 128 points to non-existent inode 6738, would junk entry
entry "497.test" in directory inode 128 points to non-existent inode 6739, would junk entry
entry "498.test" in directory inode 128 points to non-existent inode 6740, would junk entry
entry "499.test" in directory inode 128 points to non-existent inode 6741, would junk entry
entry "500.test" in directory inode 128 points to non-existent inode 6742, would junk entry
entry "501.test" in directory inode 128 points to non-existent inode 6743, would junk entry
entry "502.test" in directory inode 128 points to non-existent inode 6744, would junk entry
entry "503.test" in directory inode 128 points to non-existent inode 6745, would junk entry
entry "504.test" in directory inode 128 points to non-existent inode 6746, would junk entry
entry "505.test" in directory inode 128 points to non-existent inode 6747, would junk entry
entry "506.test" in directory inode 128 points to non-existent inode 6748, would junk entry
entry "507.test" in directory inode 128 points to non-existent inode 6749, would junk entry
entry "508.test" in directory inode 128 points to non-existent inode 6750, would junk entry
entry "509.test" in directory inode 128 points to non-existent inode 6751, would junk entry
entry "510.test" in directory inode 128 points to non-existent inode 7840, would junk entry
entry "511.test" in directory inode 128 points to non-existent inode 7841, would junk entry
entry "512.test" in directory inode 128 points to non-existent inode 7842, would junk entry
entry "513.test" in directory inode 128 points to non-existent inode 7843, would junk entry
entry "514.test" in directory inode 128 points to non-existent inode 7844, would junk entry
entry "515.test" in directory inode 128 points to non-existent inode 7845, would junk entry
entry "516.test" in directory inode 128 points to non-existent inode 7846, would junk entry
entry "517.test" in directory inode 128 points to non-existent inode 7847, would junk entry
entry "518.test" in directory inode 128 points to non-existent inode 7848, would junk entry
entry "519.test" in directory inode 128 points to non-existent inode 7849, would junk entry
entry "520.test" in directory inode 128 points to non-existent inode 7850, would junk entry
entry "521.test" in directory inode 128 points to non-existent inode 7851, would junk entry
entry "522.test" in directory inode 128 points to non-existent inode 7852, would junk entry
entry "523.test" in directory inode 128 points to non-existent inode 7853, would junk entry
entry "524.test" in directory inode 128 points to non-existent inode 7854, would junk entry
entry "525.test" in directory inode 128 points to non-existent inode 7855, would junk entry
entry "526.test" in directory inode 128 points to non-existent inode 7856, would junk entry
entry "527.test" in directory inode 128 points to non-existent inode 7857, would junk entry
entry "528.test" in directory inode 128 points to non-existent inode 7858, would junk entry
entry "529.test" in directory inode 128 points to non-existent inode 7859, would junk entry
entry "530.test" in directory inode 128 points to non-existent inode 7860, would junk entry
entry "531.test" in directory inode 128 points to non-existent inode 7861, would junk entry
entry "532.test" in directory inode 128 points to non-existent inode 7862, would junk entry
entry "533.test" in directory inode 128 points to non-existent inode 7863, would junk entry
entry "534.test" in directory inode 128 points to non-existent inode 7864, would junk entry
entry "535.test" in directory inode 128 points to non-existent inode 7865, would junk entry
entry "536.test" in directory inode 128 points to non-existent inode 7866, would junk entry
entry "537.test" in directory inode 128 points to non-existent inode 7867, would junk entry
entry "538.test" in directory inode 128 points to non-existent inode 7868, would junk entry
entry "539.test" in directory inode 128 points to non-existent inode 7869, would junk entry
entry "540.test" in directory inode 128 points to non-existent inode 7870, would junk entry
entry "541.test" in directory inode 128 points to non-existent inode 7871, would junk entry
entry "542.test" in directory inode 128 points to non-existent inode 7872, would junk entry
entry "543.test" in directory inode 128 points to non-existent inode 7873, would junk entry
entry "544.test" in directory inode 128 points to non-existent inode 7874, would junk entry
entry "545.test" in directory inode 128 points to non-existent inode 7875, would junk entry
entry "546.test" in directory inode 128 points to non-existent inode 7876, would junk entry
entry "547.test" in directory inode 128 points to non-existent inode 7877, would junk entry
entry "548.test" in directory inode 128 points to non-existent inode 7878, would junk entry
entry "549.test" in directory inode 128 points to non-existent inode 7879, would junk entry
entry "550.test" in directory inode 128 points to non-existent inode 7880, would junk entry
entry "551.test" in directory inode 128 points to non-existent inode 7881, would junk entry
entry "552.test" in directory inode 128 points to non-existent inode 7882, would junk entry
entry "553.test" in directory inode 128 points to non-existent inode 7883, would junk entry
entry "554.test" in directory inode 128 points to non-existent inode 7884, would junk entry
entry "555.test" in directory inode 128 points to non-existent inode 7885, would junk entry
entry "556.test" in directory inode 128 points to non-existent inode 7886, would junk entry
entry "557.test" in directory inode 128 points to non-existent inode 7887, would junk entry
entry "558.test" in directory inode 128 points to non-existent inode 7888, would junk entry
entry "559.test" in directory inode 128 points to non-existent inode 7889, would junk entry
entry "560.test" in directory inode 128 points to non-existent inode 7890, would junk entry
entry "561.test" in directory inode 128 points to non-existent inode 7891, would junk entry
entry "562.test" in directory inode 128 points to non-existent inode 7892, would junk entry
entry "563.test" in directory inode 128 points to non-existent inode 7893, would junk entry
entry "564.test" in directory inode 128 points to non-existent inode 7894, would junk entry
entry "565.test" in directory inode 128 points to non-existent inode 7895, would junk entry
entry "566.test" in directory inode 128 points to non-existent inode 7896, would junk entry
entry "567.test" in directory inode 128 points to non-existent inode 7897, would junk entry
entry "568.test" in directory inode 128 points to non-existent inode 7898, would junk entry
entry "569.test" in directory inode 128 points to non-existent inode 7899, would junk entry
entry "570.test" in directory inode 128 points to non-existent inode 7900, would junk entry
entry "571.test" in directory inode 128 points to non-existent inode 7901, would junk entry
entry "572.test" in directory inode 128 points to non-existent inode 7902, would junk entry
entry "573.test" in directory inode 128 points to non-existent inode 7903, would junk entry
entry "574.test" in directory inode 128 points to non-existent inode 10016, would junk entry
entry "575.test" in directory inode 128 points to non-existent inode 10017, would junk entry
entry "576.test" in directory inode 128 points to non-existent inode 10018, would junk entry
entry "577.test" in directory inode 128 points to non-existent inode 10019, would junk entry
entry "578.test" in directory inode 128 points to non-existent inode 10020, would junk entry
entry "579.test" in directory inode 128 points to non-existent inode 10021, would junk entry
entry "580.test" in directory inode 128 points to non-existent inode 10022, would junk entry
entry "581.test" in directory inode 128 points to non-existent inode 10023, would junk entry
entry "582.test" in directory inode 128 points to non-existent inode 10024, would junk entry
entry "583.test" in directory inode 128 points to non-existent inode 10025, would junk entry
entry "584.test" in directory inode 128 points to non-existent inode 10026, would junk entry
entry "585.test" in directory inode 128 points to non-existent inode 10027, would junk entry
entry "586.test" in directory inode 128 points to non-existent inode 10028, would junk entry
entry "587.test" in directory inode 128 points to non-existent inode 10029, would junk entry
entry "588.test" in directory inode 128 points to non-existent inode 10030, would junk entry
entry "589.test" in directory inode 128 points to non-existent inode 10031, would junk entry
entry "590.test" in directory inode 128 points to non-existent inode 10032, would junk entry
entry "591.test" in directory inode 128 points to non-existent inode 10033, would junk entry
entry "592.test" in directory inode 128 points to non-existent inode 10034, would junk entry
entry "593.test" in directory inode 128 points to non-existent inode 10035, would junk entry
entry "594.test" in directory inode 128 points to non-existent inode 10036, would junk entry
entry "595.test" in directory inode 128 points to non-existent inode 10037, would junk entry
entry "596.test" in directory inode 128 points to non-existent inode 10038, would junk entry
entry "597.test" in directory inode 128 points to non-existent inode 10039, would junk entry
entry "598.test" in directory inode 128 points to non-existent inode 10040, would junk entry
entry "599.test" in directory inode 128 points to non-existent inode 10041, would junk entry
entry "600.test" in directory inode 128 points to non-existent inode 10042, would junk entry
entry "601.test" in directory inode 128 points to non-existent inode 10043, would junk entry
entry "602.test" in directory inode 128 points to non-existent inode 10044, would junk entry
entry "603.test" in directory inode 128 points to non-existent inode 10045, would junk entry
entry "604.test" in directory inode 128 points to non-existent inode 10046, would junk entry
entry "605.test" in directory inode 128 points to non-existent inode 10047, would junk entry
entry "606.test" in directory inode 128 points to non-existent inode 10048, would junk entry
unknown magic number 0xd2f1 for block 8388608 in directory inode 128
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 2319, would move to lost+found
disconnected inode 2320, would move to lost+found
disconnected inode 2321, would move to lost+found
disconnected inode 2322, would move to lost+found
disconnected inode 2323, would move to lost+found
disconnected inode 2324, would move to lost+found
disconnected inode 2325, would move to lost+found
disconnected inode 2326, would move to lost+found
disconnected inode 2327, would move to lost+found
disconnected inode 2328, would move to lost+found
disconnected inode 2329, would move to lost+found
disconnected inode 2330, would move to lost+found
disconnected inode 2331, would move to lost+found
disconnected inode 2332, would move to lost+found
disconnected inode 2333, would move to lost+found
disconnected inode 2334, would move to lost+found
disconnected inode 2335, would move to lost+found
disconnected inode 2336, would move to lost+found
disconnected inode 2337, would move to lost+found
disconnected inode 2338, would move to lost+found
disconnected inode 2339, would move to lost+found
disconnected inode 2340, would move to lost+found
disconnected inode 2341, would move to lost+found
disconnected inode 2342, would move to lost+found
disconnected inode 2343, would move to lost+found
disconnected inode 2344, would move to lost+found
disconnected inode 2345, would move to lost+found
disconnected inode 2346, would move to lost+found
disconnected inode 2347, would move to lost+found
disconnected inode 2348, would move to lost+found
disconnected inode 2349, would move to lost+found
disconnected inode 2350, would move to lost+found
disconnected inode 2351, would move to lost+found
disconnected inode 2352, would move to lost+found
disconnected inode 2353, would move to lost+found
disconnected inode 2354, would move to lost+found
disconnected inode 2355, would move to lost+found
disconnected inode 2356, would move to lost+found
disconnected inode 2357, would move to lost+found
disconnected inode 2358, would move to lost+found
disconnected inode 2359, would move to lost+found
disconnected inode 2360, would move to lost+found
disconnected inode 2361, would move to lost+found
disconnected inode 2362, would move to lost+found
disconnected inode 2363, would move to lost+found
disconnected inode 2364, would move to lost+found
disconnected inode 2365, would move to lost+found
disconnected inode 2366, would move to lost+found
disconnected inode 2367, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Issue on kernel 2.6.35.9 vanilla
2010-12-22 7:00 ` naveen yadav
@ 2010-12-23 5:19 ` naveen yadav
0 siblings, 0 replies; 5+ messages in thread
From: naveen yadav @ 2010-12-23 5:19 UTC (permalink / raw)
To: Dave Chinner, xfs
Hi Dave,
The question you ask about log difference, the reason is I just reboot
my PC and
again reconnect my corrupted disk again,
FYI, I already send rest of info in my previous mail, If you need more
info, i will provide
Thanks
On Wed, Dec 22, 2010 at 12:30 PM, naveen yadav <yad.naveen@gmail.com> wrote:
> Thanks a lot Dave,
>
> Please find attached log for command xfs_repair -n.
>
> Thanks a lot
>
> On Wed, Dec 22, 2010 at 11:07 AM, Dave Chinner <david@fromorbit.com> wrote:
>> On Wed, Dec 22, 2010 at 10:27:16AM +0530, naveen yadav wrote:
>>> Hi Dave,
>>>
>>> Please find attached log as suggested by you.
>>>
>>> Kind regards
>>> Naveen
>>>
>>> On Wed, Dec 22, 2010 at 3:01 AM, Dave Chinner <david@fromorbit.com> wrote:
>>> > 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]
>> .....
>>> >> 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
>>
>> This is not in your dmesg log. When did it actually happen? Before
>> the hung task timer started to trip? From your log:
>>
>> scsi 5:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 2
>> sd 5:0:0:0: Attached scsi generic sg1 type 0
>> sd 5:0:0:0: [sdb] 15625216 512-byte logical blocks: (8.00 GB/7.45 GiB)
>> sd 5:0:0:0: [sdb] Write Protect is off
>> sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
>> sd 5:0:0:0: [sdb] Assuming drive cache: write through
>> sd 5:0:0:0: [sdb] Assuming drive cache: write through
>> sdb: sdb1 sdb2
>> sd 5:0:0:0: [sdb] Assuming drive cache: write through
>> sd 5:0:0:0: [sdb] Attached SCSI removable disk
>> SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
>> XFS mounting filesystem sdb2
>> Starting XFS recovery on filesystem: sdb2 (logdev: internal)
>> Ending XFS recovery on filesystem: sdb2 (logdev: internal)
>> SELinux: initialized (dev sdb2, type xfs), uses xattr
>> INFO: task gvfs-gdu-volume:2311 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> gvfs-gdu-volu D 00000026 0 2311 1 0x00000080
>> c6cf9b2c 00000086 a41cc623 00000026 c0a25e00 c0a25e00 c0a25e00 c0a25e00
>> d1290f54 c0a25e00 c0a25e00 000336ad 00000000 cd871c00 00000026 d1290cd0
>> 00000000 cd8d2a08 cd8d2a00 7fffffff 7fffffff c6cf9b70 c0781c43 00000000
>> Call Trace:
>> [<c0781c43>] schedule_timeout+0x1b/0x95
>> [<c07824d1>] __down_common+0x82/0xb9
>> [<e0e28ae8>] ? _xfs_buf_find+0x122/0x1b8 [xfs]
>> [<c0782567>] __down+0x17/0x19
>> [<c045827c>] down+0x27/0x37
>> [<e0e278da>] xfs_buf_lock+0x67/0x93 [xfs]
>> [<e0e28ae8>] _xfs_buf_find+0x122/0x1b8 [xfs]
>> [<e0e28bde>] xfs_buf_get+0x60/0x149 [xfs]
>> [<e0e28ce9>] xfs_buf_read+0x22/0xb0 [xfs]
>> [<e0e1ffa9>] xfs_trans_read_buf+0x53/0x2e9 [xfs]
>> [<e0dfd151>] xfs_da_do_buf+0x411/0x628 [xfs]
>> [<e0dfe0d3>] ? xfs_da_node_lookup_int+0x52/0x207 [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
>> [<c04dbd59>] do_last+0x186/0x49f
>> [<c04dc415>] do_filp_open+0x1bd/0x459
>> [<c045b191>] ? timekeeping_get_ns+0x16/0x54
>> [<c05a9170>] ? might_fault+0x1e/0x20
>> [<c04e479a>] ? alloc_fd+0x58/0xbe
>> [<c04d1941>] do_sys_open+0x4d/0xe4
>> [<c047d0f4>] ? audit_syscall_entry+0x12a/0x14c
>> [<c04d1a24>] sys_open+0x23/0x2b
>> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>>
>> You've got a gvfs (gnome-vfs?) process stuck waiting on a buffer
>> lock. The onyl way I can see it getting stuck here is if it the
>> buffer has not been unlocked somewhere. It's possible that it is
>> stuck on the same buffer that the corruption error came from,
>> but the corrupted buffer is unlocked in the error handling path.
>> what does `xfs_repair -n` tell about the filesytsem?
>>
>> FWIW, later on:
>>
>> ......
>> INFO: task gvfsd-trash:1891 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> gvfsd-trash D 00000026 0 1891 1 0x00000080
>>
>> gvfs-trashd gets stuck on a mutex during a path walk which is
>> probably held by the above directory read.
>>
>> ....
>> INFO: task gvfs-gdu-volume:2321 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> gvfs-gdu-volu D 00000026 0 2321 1 0x00000088
>>
>> As does this one.
>>
>> ....
>>
>> gvfs-gdu-volu D 00000026 0 1889 1 0x00000080
>> cda3df10 00000086 a422923c 00000026 c0a25e00 c0a25e00 c0a25e00 c0a25e00
>> cd936904 c0a25e00 c0a25e00 000b9ea1 00000000 cda24400 00000026 cd936680
>> 00ae3000 c34c01a4 c34c019c cd936680 c34c01a0 cda3df44 c0782093 c34c01ac
>> Call Trace:
>> [<c0782093>] __mutex_lock_common+0xe8/0x137
>> [<c0782113>] __mutex_lock_killable_slowpath+0x17/0x19
>> [<c0782160>] ? mutex_lock_killable+0x32/0x45
>> [<c0782160>] mutex_lock_killable+0x32/0x45
>> [<c04deb0a>] vfs_readdir+0x46/0x94
>> [<c04de814>] ? filldir64+0x0/0xf5
>> [<c04debca>] sys_getdents64+0x72/0xb2
>> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>>
>> And this one, too.
>>
>> .....
>> ls D 00000000 0 2325 2044 0x00000080
>> c6d03f10 00200086 00000000 00000000 c0a25e00 c0a25e00 c0a25e00 c0a25e00
>> cdacb5c4 c0a25e00 c0a25e00 d6779fa1 00000029 00000000 00000029 cdacb340
>> 00000001 c34c01a4 c34c019c cdacb340 c34c01a0 c6d03f44 c0782093 c34c01ac
>> Call Trace:
>> [<c0782093>] __mutex_lock_common+0xe8/0x137
>> [<c0782113>] __mutex_lock_killable_slowpath+0x17/0x19
>> [<c0782160>] ? mutex_lock_killable+0x32/0x45
>> [<c0782160>] mutex_lock_killable+0x32/0x45
>> [<c04deb0a>] vfs_readdir+0x46/0x94
>> [<c04de814>] ? filldir64+0x0/0xf5
>> [<c04debca>] sys_getdents64+0x72/0xb2
>> [<c0407fd8>] sysenter_do_call+0x12/0x2d
>>
>> And finally, there is an ls process that is hung, stuck on a
>> directory mutex. Is this the one you were seeing hang rather than
>> whatever generated the corrupion report?
>>
>> Cheers,
>>
>> Dave.
>> --
>> Dave Chinner
>> david@fromorbit.com
>>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-12-23 5:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTim8VD2NQ1a2t47jOA+MyyVGWejymoJh41jfrRkA@mail.gmail.com>
2010-12-21 14:11 ` Issue on kernel 2.6.35.9 vanilla naveen yadav
2010-12-21 21:31 ` Dave Chinner
[not found] ` <AANLkTik3batsHu57QDUWmspf7C8As75t3mUO6QG_i040@mail.gmail.com>
2010-12-22 4:57 ` naveen yadav
[not found] ` <20101222053730.GG4907@dastard>
2010-12-22 7:00 ` naveen yadav
2010-12-23 5:19 ` naveen yadav
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox