On Sun, 2015-11-15 at 09:29 +0800, Qu Wenruo wrote: > > > If type is wrong, all the extents inside the chunk should be > > > reported > > > as > > > mismatch type with chunk. > > Isn't that the case? At least there are so many reported extents... > > If you posted all the output Sure, I posted everything that the dump gave :)
> , that's just a little more than nothing. > Just tens of error reported, compared to millions of extents. > And in your case, if a chunk is really bad, it will report about 65K > errors. I see.. > I think it's a btrfsck issue, at least from the dump info, your > extent > tree is OK. > And if there is no other error reported from btrfsck, your filesystem > should be OK. Nope.. there were no further errors. > > In any case, I'll keep the fs in question for a while, so that I > > can do > > verifications in case you have patches. > > Nice. Just tell me if you have something. btw: I saw these: Nov 15 02:01:42 heisenberg kernel: INFO: task btrfs-transacti:28379 blocked for more than 120 seconds. Nov 15 02:01:42 heisenberg kernel: Not tainted 4.2.0-1-amd64 #1 Nov 15 02:01:42 heisenberg kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 15 02:01:42 heisenberg kernel: btrfs-transacti D ffffffff8109a1b0 0 28379 2 0x00000000 Nov 15 02:01:42 heisenberg kernel: ffff88016e3e6500 0000000000000046 000000000000007a ffff88040be88f00 Nov 15 02:01:42 heisenberg kernel: 0000000000002659 ffff880138070000 ffff88041e355840 7fffffffffffffff Nov 15 02:01:42 heisenberg kernel: ffffffff815508e0 ffff88013806fbb8 0007ffffffffffff ffffffff815500ff Nov 15 02:01:42 heisenberg kernel: Call Trace: Nov 15 02:01:42 heisenberg kernel: [<ffffffff815508e0>] ? bit_wait_timeout+0x70/0x70 Nov 15 02:01:42 heisenberg kernel: [<ffffffff815500ff>] ? schedule+0x2f/0x70 Nov 15 02:01:42 heisenberg kernel: [<ffffffff81552bc7>] ? schedule_timeout+0x1f7/0x290 Nov 15 02:01:42 heisenberg kernel: [<ffffffffa02be6f2>] ? extent_write_cache_pages.isra.28.constprop.43+0x222/0x330 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffff8101c325>] ? read_tsc+0x5/0x10 Nov 15 02:01:42 heisenberg kernel: [<ffffffff815508e0>] ? bit_wait_timeout+0x70/0x70 Nov 15 02:01:42 heisenberg kernel: [<ffffffff8154f7ad>] ? io_schedule_timeout+0x9d/0x110 Nov 15 02:01:42 heisenberg kernel: [<ffffffff81550915>] ? bit_wait_io+0x35/0x60 Nov 15 02:01:42 heisenberg kernel: [<ffffffff815504ca>] ? __wait_on_bit+0x5a/0x90 Nov 15 02:01:42 heisenberg kernel: [<ffffffff81152496>] ? find_get_pages_tag+0x116/0x150 Nov 15 02:01:42 heisenberg kernel: [<ffffffff811513a6>] ? wait_on_page_bit+0xb6/0xc0 Nov 15 02:01:42 heisenberg kernel: [<ffffffff810a9b20>] ? autoremove_wake_function+0x40/0x40 Nov 15 02:01:42 heisenberg kernel: [<ffffffff81151477>] ? filemap_fdatawait_range+0xc7/0x140 Nov 15 02:01:42 heisenberg kernel: [<ffffffffa02b9a43>] ? btrfs_wait_ordered_range+0x73/0x110 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa02e3c1d>] ? btrfs_wait_cache_io+0x5d/0x1e0 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa028e7bc>] ? btrfs_start_dirty_block_groups+0x17c/0x3f0 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa029ee84>] ? btrfs_commit_transaction+0x1b4/0xa90 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa029f7f0>] ? start_transaction+0x90/0x580 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa029a654>] ? transaction_kthread+0x224/0x240 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffffa029a430>] ? btrfs_cleanup_transaction+0x510/0x510 [btrfs] Nov 15 02:01:42 heisenberg kernel: [<ffffffff8108aa41>] ? kthread+0xc1/0xe0 Nov 15 02:01:42 heisenberg kernel: [<ffffffff8108a980>] ? kthread_create_on_node+0x170/0x170 Nov 15 02:01:42 heisenberg kernel: [<ffffffff81553e5f>] ? ret_from_fork+0x3f/0x70 Nov 15 02:01:42 heisenberg kernel: [<ffffffff8108a980>] ? kthread_create_on_node+0x170/0x170 Nov 15 02:03:42 heisenberg kernel: INFO: task btrfs-transacti:28379 blocked for more than 120 seconds. Nov 15 02:03:42 heisenberg kernel: Not tainted 4.2.0-1-amd64 #1 Nov 15 02:03:42 heisenberg kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 15 02:03:42 heisenberg kernel: btrfs-transacti D ffffffff8109a1b0 0 28379 2 0x00000000 Nov 15 02:03:42 heisenberg kernel: ffff88016e3e6500 0000000000000046 000000000000007a ffff88040be88f00 Nov 15 02:03:42 heisenberg kernel: 0000000000002659 ffff880138070000 ffff88041e355840 7fffffffffffffff Nov 15 02:03:42 heisenberg kernel: ffffffff815508e0 ffff88013806fbb8 0007ffffffffffff ffffffff815500ff Nov 15 02:03:42 heisenberg kernel: Call Trace: Nov 15 02:03:42 heisenberg kernel: [<ffffffff815508e0>] ? bit_wait_timeout+0x70/0x70 Nov 15 02:03:42 heisenberg kernel: [<ffffffff815500ff>] ? schedule+0x2f/0x70 Nov 15 02:03:42 heisenberg kernel: [<ffffffff81552bc7>] ? schedule_timeout+0x1f7/0x290 Nov 15 02:03:42 heisenberg kernel: [<ffffffffa02be6f2>] ? extent_write_cache_pages.isra.28.constprop.43+0x222/0x330 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffff8101c325>] ? read_tsc+0x5/0x10 Nov 15 02:03:42 heisenberg kernel: [<ffffffff815508e0>] ? bit_wait_timeout+0x70/0x70 Nov 15 02:03:42 heisenberg kernel: [<ffffffff8154f7ad>] ? io_schedule_timeout+0x9d/0x110 Nov 15 02:03:42 heisenberg kernel: [<ffffffff81550915>] ? bit_wait_io+0x35/0x60 Nov 15 02:03:42 heisenberg kernel: [<ffffffff815504ca>] ? __wait_on_bit+0x5a/0x90 Nov 15 02:03:42 heisenberg kernel: [<ffffffff81152496>] ? find_get_pages_tag+0x116/0x150 Nov 15 02:03:42 heisenberg kernel: [<ffffffff811513a6>] ? wait_on_page_bit+0xb6/0xc0 Nov 15 02:03:42 heisenberg kernel: [<ffffffff810a9b20>] ? autoremove_wake_function+0x40/0x40 Nov 15 02:03:42 heisenberg kernel: [<ffffffff81151477>] ? filemap_fdatawait_range+0xc7/0x140 Nov 15 02:03:42 heisenberg kernel: [<ffffffffa02b9a43>] ? btrfs_wait_ordered_range+0x73/0x110 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa02e3c1d>] ? btrfs_wait_cache_io+0x5d/0x1e0 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa028e7bc>] ? btrfs_start_dirty_block_groups+0x17c/0x3f0 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa029ee84>] ? btrfs_commit_transaction+0x1b4/0xa90 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa029f7f0>] ? start_transaction+0x90/0x580 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa029a654>] ? transaction_kthread+0x224/0x240 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffffa029a430>] ? btrfs_cleanup_transaction+0x510/0x510 [btrfs] Nov 15 02:03:42 heisenberg kernel: [<ffffffff8108aa41>] ? kthread+0xc1/0xe0 Nov 15 02:03:42 heisenberg kernel: [<ffffffff8108a980>] ? kthread_create_on_node+0x170/0x170 Nov 15 02:03:42 heisenberg kernel: [<ffffffff81553e5f>] ? ret_from_fork+0x3f/0x70 Nov 15 02:03:42 heisenberg kernel: [<ffffffff8108a980>] ? kthread_create_on_node+0x170/0x170 Nov 15 04:18:37 heisenberg kernel: virbr1: port 2(vnet0) entered disabled state Nov 15 04:18:37 heisenberg kernel: device vnet0 left promiscuous mode Nov 15 04:18:37 heisenberg kernel: virbr1: port 2(vnet0) entered disabled state Is that anything to worry about? And any way to find out to which filesystem that process corresponds? At least I've never seen btrfs-transacti to hang... and since nothing than the cp -a from on to the other disk is doing anything on the two HDDs, I was a bit surprised to see that happen Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
