All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Victor Helmholtz <victor.helmholtz@gmail.com>, dm-crypt@saout.de
Cc: device-mapper development <dm-devel@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [dm-crypt] Dm-integrity freeze
Date: Thu, 7 Mar 2019 17:37:10 +0100	[thread overview]
Message-ID: <9d19e5b1-b76f-27da-fa4a-f3a83e6e2791@gmail.com> (raw)
In-Reply-To: <5D8A23C5-B6AD-48EA-B0AD-AD1BD1A2B97B@gmail.com>

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
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt
> 

  reply	other threads:[~2019-03-07 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 15:26 [dm-crypt] Dm-integrity freeze Victor Helmholtz
2019-03-07 16:37 ` Milan Broz [this message]
2019-05-21  8:43   ` [dm-crypt] [dm-devel] " Hans van Kranenburg
2019-05-21  8:43     ` [dm-crypt] " Hans van Kranenburg
2019-05-21 20:33     ` [dm-crypt] [dm-devel] " Hans van Kranenburg
2019-05-21 20:33       ` [dm-crypt] " Hans van Kranenburg
2019-05-21 22:07       ` Mike Snitzer
2019-05-21 22:07         ` Mike Snitzer
2019-05-22  7:52         ` [dm-crypt] " Hans van Kranenburg
2019-05-22  7:52           ` Hans van Kranenburg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d19e5b1-b76f-27da-fa4a-f3a83e6e2791@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=victor.helmholtz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.