Re: [dm-crypt] Dm-integrity freeze

Hi,

from the full log it seems that it is stuck in tgtd (iSCSI).

Anyway, this is device-mapper, dm-devel is better list here.
(added to cc + Mikulas)

m.

On 3/7/19 4:26 PM, Victor Helmholtz wrote:
> Hi
> 
> I have recently had a problem with my server: all writes to RAID drives were frozen and I had to force-reboot it. I looked at kernel logs and I think dm-integrity might be source of the problem. Could anyone help me understand meaning of following messages (this message was repeated 8 times, full kernel log is here: https://pastebin.com/DMgMtNJq ):
> 
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.498048] INFO: task kworker/0:112:26760 blocked for more than 120 seconds.
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.499784]       Not tainted 4.19.0-2-amd64 #1 Debian 4.19.16-1
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.501222] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.503095] kworker/0:112   D    0 26760      2 0x80000080
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.504424] Workqueue: dm-integrity-metadata integrity_bio_wait [dm_integrity]
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.506149] Call Trace:
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.506782]  ? __schedule+0x2a2/0x870
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.507706]  schedule+0x28/0x80
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.508484]  io_schedule+0x12/0x40
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.509321]  wait_and_add_new_range+0x89/0xa0 [dm_integrity]
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.510709]  dm_integrity_map_continue+0xe71/0x1020 [dm_integrity]
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.512193]  ? __switch_to_asm+0x40/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.513149]  ? __switch_to_asm+0x34/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.514105]  ? __switch_to_asm+0x40/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.515088]  ? __switch_to_asm+0x40/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.516048]  ? __switch_to_asm+0x34/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.517000]  ? __switch_to_asm+0x40/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.517978]  ? __switch_to_asm+0x34/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.518968]  ? __switch_to_asm+0x34/0x70
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.519926]  ? __switch_to+0x8c/0x440
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.520822]  process_one_work+0x1a7/0x3a0
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.521798]  worker_thread+0x30/0x390
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.522725]  ? pwq_unbound_release_workfn+0xd0/0xd0
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.523901]  kthread+0x112/0x130
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.524691]  ? kthread_bind+0x30/0x30
> Mar  1 23:48:21 unassigned-hostname kernel: [369732.525584]  ret_from_fork+0x35/0x40
> 
> Is this a bug in kernel or do I have some problems with hardware?
> 
> Regards
> Victor
> 
> _______________________________________________
> dm-crypt mailing list
> [email protected]
> https://www.saout.de/mailman/listinfo/dm-crypt
>