error -lock in zfs send
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Native ZFS for Linux |
Fix Released
|
Unknown
|
|||
zfs-linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
zfs send stop working. the process did not produce output. checked by mbuffer log
in kernel.log:
Oct 15 07:25:53 zfs-cis kernel: [479439.151281] INFO: task zfs:8708 blocked for more than 120 seconds.
Oct 15 07:25:53 zfs-cis kernel: [479439.156980] Tainted: P OE 4.4.0-96-generic #119-Ubuntu
Oct 15 07:25:53 zfs-cis kernel: [479439.162688] "echo 0 > /proc/sys/
Oct 15 07:25:53 zfs-cis kernel: [479439.173974] zfs D ffff88197bd77318 0 8708 8141 0x00000000
Oct 15 07:25:53 zfs-cis kernel: [479439.173981] ffff88197bd77318 ffffffff810c3dc2 ffff8820374cf000 ffff881b645ff000
Oct 15 07:25:53 zfs-cis kernel: [479439.173985] ffff88197bd78000 0000000000792c6d ffff882030aa4ac8 0000000000000000
Oct 15 07:25:53 zfs-cis kernel: [479439.173989] ffff88101dac1840 ffff88197bd77330 ffffffff8183f165 ffff882030aa4a00
Oct 15 07:25:53 zfs-cis kernel: [479439.173993] Call Trace:
Oct 15 07:25:53 zfs-cis kernel: [479439.174006] [<ffffffff810c3
Oct 15 07:25:53 zfs-cis kernel: [479439.174023] [<ffffffff8183f
Oct 15 07:25:53 zfs-cis kernel: [479439.174045] [<ffffffffc03d7
Oct 15 07:25:53 zfs-cis kernel: [479439.174051] [<ffffffff810c4
Oct 15 07:25:53 zfs-cis kernel: [479439.174115] [<ffffffffc0503
Oct 15 07:25:53 zfs-cis kernel: [479439.174178] [<ffffffffc0542
Oct 15 07:25:53 zfs-cis kernel: [479439.174223] [<ffffffffc0502
Oct 15 07:25:53 zfs-cis kernel: [479439.174267] [<ffffffffc0503
Oct 15 07:25:53 zfs-cis kernel: [479439.174311] [<ffffffffc0505
Oct 15 07:25:53 zfs-cis kernel: [479439.174356] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174365] [<ffffffffc03d4
Oct 15 07:25:53 zfs-cis kernel: [479439.174409] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174462] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174503] [<ffffffffc0508
Oct 15 07:25:53 zfs-cis kernel: [479439.174542] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174579] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174616] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174653] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174690] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174726] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174762] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174799] [<ffffffffc0508
Oct 15 07:25:53 zfs-cis kernel: [479439.174835] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174871] [<ffffffffc0507
Oct 15 07:25:53 zfs-cis kernel: [479439.174908] [<ffffffffc0504
Oct 15 07:25:53 zfs-cis kernel: [479439.174944] [<ffffffffc0508
Oct 15 07:25:53 zfs-cis kernel: [479439.174981] [<ffffffffc0504
Oct 15 07:25:53 zfs-cis kernel: [479439.175017] [<ffffffffc0502
Oct 15 07:25:53 zfs-cis kernel: [479439.175060] [<ffffffffc0505
Oct 15 07:25:53 zfs-cis kernel: [479439.175129] [<ffffffffc0572
Oct 15 07:25:53 zfs-cis kernel: [479439.175143] [<ffffffffc03d4
Oct 15 07:25:53 zfs-cis kernel: [479439.175207] [<ffffffffc0576
Oct 15 07:25:53 zfs-cis kernel: [479439.175218] [<ffffffff81223
Oct 15 07:25:53 zfs-cis kernel: [479439.175225] [<ffffffff81080
Oct 15 07:25:53 zfs-cis kernel: [479439.175232] [<ffffffff81224
Oct 15 07:25:53 zfs-cis kernel: [479439.175242] [<ffffffff81843
Changed in zfs-linux (Ubuntu): | |
status: | New → Incomplete |
importance: | Undecided → Medium |
assignee: | nobody → Colin Ian King (colin-king) |
Changed in zfs: | |
status: | Unknown → New |
Changed in zfs-linux (Ubuntu): | |
assignee: | Colin Ian King (colin-king) → nobody |
Changed in zfs: | |
status: | New → Fix Released |
This stack trace was also reported in bug https:/ /github. com/zfsonlinux/ zfs/issues/ 6917 in log https:/ /github. com/zfsonlinux/ zfs/files/ 1686101/ kern.log. 2.gz
Is this issue still occurring?
1. what is your ZFS configuration (number of drives?)
2. size of your system (total memory, free memory).
3. Do your drive(s) suffer from large I/O latencies?
- what is the output from iostat -mx when you are loading the system when issues like this occur?