From: Mike Snitzer <snitzer@redhat.com>
To: Hans van Kranenburg <hans@knorrie.org>
Cc: Milan Broz <gmazyland@gmail.com>,
Victor Helmholtz <victor.helmholtz@gmail.com>,
dm-crypt@saout.de,
device-mapper development <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [dm-crypt] Dm-integrity freeze
Date: Tue, 21 May 2019 18:07:36 -0400 [thread overview]
Message-ID: <20190521220736.GB30736@redhat.com> (raw)
In-Reply-To: <33d155ac-9b09-c8b0-3df1-88063dac964f@knorrie.org>
On Tue, May 21 2019 at 4:33pm -0400,
Hans van Kranenburg <hans@knorrie.org> wrote:
> Hi,
>
> On 5/21/19 10:43 AM, Hans van Kranenburg wrote:
> > Hi,
> >
> > I'm seeing the same lockup, also 4.19. This is mdadm RAID10 on top of 4x
> > a partition with only dm-integrity.
> >
> > It just happened out of the blue, no heavy load or anything. All IO to
> > it is frozen now.
> >
> > [...]
>
> There it is again... dmesg dump below. All cpus on 100% iowait.
>
> It's triggered after a few minutes by running some Windows 2019 server
> install (ugh, don't ask) in a Xen HVM domU, which writes into a raw
> sparse file on a btrfs filesystem on LVM on mdadm RAID10 on 4x
> dm-integrity (wheeee!!)...
>
> This morning it was triggered a few minutes after starting an old
> windows 2008 server image that I copied to this machine.
>
> When running only other Linux vms, and when copying data onto
> filesystems that live in LVM logical volumes I haven't seen this problem
> yet, at all, in the last few weeks that this machine is running.
>
> I noticed there's a "dm integrity: fix deadlock with overlapping I/O"
> fix in a later 4.19. Is there any chance this is related? I have no
> idea, but any hints or suggestions about what to try would be appreciated.
Yes, all your hung tasks are hung in wait_and_add_new_range().
Please use that later 4.19 or apply commit 4ed319c6ac08 ("dm integrity:
fix deadlock with overlapping I/O")
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Hans van Kranenburg <hans@knorrie.org>
Cc: dm-crypt@saout.de,
device-mapper development <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Milan Broz <gmazyland@gmail.com>,
Victor Helmholtz <victor.helmholtz@gmail.com>
Subject: Re: Dm-integrity freeze
Date: Tue, 21 May 2019 18:07:36 -0400 [thread overview]
Message-ID: <20190521220736.GB30736@redhat.com> (raw)
In-Reply-To: <33d155ac-9b09-c8b0-3df1-88063dac964f@knorrie.org>
On Tue, May 21 2019 at 4:33pm -0400,
Hans van Kranenburg <hans@knorrie.org> wrote:
> Hi,
>
> On 5/21/19 10:43 AM, Hans van Kranenburg wrote:
> > Hi,
> >
> > I'm seeing the same lockup, also 4.19. This is mdadm RAID10 on top of 4x
> > a partition with only dm-integrity.
> >
> > It just happened out of the blue, no heavy load or anything. All IO to
> > it is frozen now.
> >
> > [...]
>
> There it is again... dmesg dump below. All cpus on 100% iowait.
>
> It's triggered after a few minutes by running some Windows 2019 server
> install (ugh, don't ask) in a Xen HVM domU, which writes into a raw
> sparse file on a btrfs filesystem on LVM on mdadm RAID10 on 4x
> dm-integrity (wheeee!!)...
>
> This morning it was triggered a few minutes after starting an old
> windows 2008 server image that I copied to this machine.
>
> When running only other Linux vms, and when copying data onto
> filesystems that live in LVM logical volumes I haven't seen this problem
> yet, at all, in the last few weeks that this machine is running.
>
> I noticed there's a "dm integrity: fix deadlock with overlapping I/O"
> fix in a later 4.19. Is there any chance this is related? I have no
> idea, but any hints or suggestions about what to try would be appreciated.
Yes, all your hung tasks are hung in wait_and_add_new_range().
Please use that later 4.19 or apply commit 4ed319c6ac08 ("dm integrity:
fix deadlock with overlapping I/O")
Mike
next prev parent reply other threads:[~2019-05-21 22:15 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
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 [this message]
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=20190521220736.GB30736@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=hans@knorrie.org \
--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.