linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@whissi.de>
To: "'LVM general discussion and development'" <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvcreate hangs forever during snapshot creation when suspending volume
Date: Tue, 2 Aug 2022 05:01:57 +0200	[thread overview]
Message-ID: <000901d8a61c$3adf2fb0$b09d8f10$@whissi.de> (raw)
In-Reply-To: <000601d8a5e6$29a770d0$7cf65270$@whissi.de>

Hi,

Zdenek Kabelac wrote:
> Now - you suggests you are able to reproduce this issue also on your bare 
> metal hw - in this case run these 3 commands  before  'lvcreate'

Here we go:

> $ dmsetup table
> devDataStore1-volMachines: 0 5368709120 linear 9:127 2048
> devDataStore2-volData: 0 11596414976 linear 259:6 2048
> devSystem-volRoot: 0 419430400 linear 8:3 50333696
> devSystem-volSwap: 0 50331648 linear 8:3 2048

> $ dmsetup info -c
> Name                      Maj Min Stat Open Targ Event  UUID
> devDataStore1-volMachines 253   1 L--w    1    1      0
LVM-AzPWjYw7Nts8ZnQyaKdjJ8cyaG0b9umSFIx2fo4zZvW8QplyYM3jNaQSFXSDMNDW
> devDataStore2-volData     253   0 L--w    1    1      0
LVM-RZtslsKN16YTBhJZE4qzFkvFQVChUKEcyUS1BwtKv3CeDUnKkTz53p8IwT5pqMnk
> devSystem-volRoot         253   3 L--w    1    1      0
LVM-TZlj0Mwy3bA5QpPVVpeO6ncufQ2Va36MgxgnvVn7fNGMme2prgc1xn9e25vua36d
> devSystem-volSwap         253   2 L--w    2    1      0
LVM-TZlj0Mwy3bA5QpPVVpeO6ncufQ2Va36Mp6kfZF6l8ubeUOo00BrK7kFGK8JvcG6X

> $ dmsetup ls --tree
> devDataStore1-volMachines (253:1)
>  L- (9:127)
> devDataStore2-volData (253:0)
>  L- (259:6)
> devSystem-volRoot (253:3)
>  L- (8:3)
> devSystem-volSwap (253:2)
>  L- (8:3)

...and during lvcreate when the system hangs:

> $ dmsetup table
> devDataStore1-volMachines: 0 5368709120 linear 9:127 2048
> devDataStore1-volMachines-real:
> devDataStore1-volMachines_snap:
> devDataStore1-volMachines_snap-cow: 0 209715200 linear 9:127 5368711168
> devDataStore2-volData: 0 11596414976 linear 259:6 2048
> devSystem-volRoot: 0 419430400 linear 8:3 50333696
> devSystem-volSwap: 0 50331648 linear 8:3 2048

> $ dmsetup info -c
> Name                               Maj Min Stat Open Targ Event  UUID
> devDataStore1-volMachines          253   1 LI-w    1    1      0
LVM-AzPWjYw7Nts8ZnQyaKdjJ8cyaG0b9umSFIx2fo4zZvW8QplyYM3jNaQSFXSDMNDW
> devDataStore1-volMachines-real     253   4 -I-w    2    0      0
LVM-AzPWjYw7Nts8ZnQyaKdjJ8cyaG0b9umSFIx2fo4zZvW8QplyYM3jNaQSFXSDMNDW-real
> devDataStore1-volMachines_snap     253   6 -I-w    0    0      0
LVM-AzPWjYw7Nts8ZnQyaKdjJ8cyaG0b9umSHue1IrGu69toKQ0ZdcbSv97i3xq5YP2v
> devDataStore1-volMachines_snap-cow 253   5 L--w    1    1      0
LVM-AzPWjYw7Nts8ZnQyaKdjJ8cyaG0b9umSHue1IrGu69toKQ0ZdcbSv97i3xq5YP2v-cow
> devDataStore2-volData              253   0 L--w    1    1      0
LVM-RZtslsKN16YTBhJZE4qzFkvFQVChUKEcyUS1BwtKv3CeDUnKkTz53p8IwT5pqMnk
> devSystem-volRoot                  253   3 L--w    1    1      0
LVM-TZlj0Mwy3bA5QpPVVpeO6ncufQ2Va36MgxgnvVn7fNGMme2prgc1xn9e25vua36d
> devSystem-volSwap                  253   2 L--w    2    1      0
LVM-TZlj0Mwy3bA5QpPVVpeO6ncufQ2Va36Mp6kfZF6l8ubeUOo00BrK7kFGK8JvcG6X

> $ dmsetup ls --tree
> devDataStore1-volMachines (253:1)
>  L- (9:127)
> devDataStore1-volMachines-real (253:4)
> devDataStore1-volMachines_snap (253:6)
> devDataStore1-volMachines_snap-cow (253:5)
>  L- (9:127)
> devDataStore2-volData (253:0)
>  L- (259:6)
> devSystem-volRoot (253:3)
>  L- (8:3)
> devSystem-volSwap (253:2)
>  L- (8:3)

> $ cat /proc/meminfo | grep Dirty
> Dirty:                0 kB

In case someone will ask: During I/O, the value increased/decreased
as expected.


Zdenek Kabelac wrote:
> Note: you could always 'experiment' without lvm2 in the picture -
> you can ran   'fsfreeze --freeze|--unfreeze'  yourself - to see whether
even 
> this command is able to finish  ?

fsfreeze caused the same problem :/

I also changed filesystem from xfs to ext4 just in case... same issue.

For testing I stopped the MDRAID and removed one NVMe disk which I
cleared and where I created a new ext4 partition. Running

  $ fsfreeze --freeze /mnt/test

returned within seconds and I was unable do any I/O against /mnt/test
as expected.

I unfreezed the filesystem and started to copy ~50GB to the volume.
After waiting 5 minutes and verifying that /proc/meminfo didn't list
any 'dirty' pages, I re-run the fsfreeze command which caused the
same issue -- system hangs. :/

I will repeat the test with the other NVMe later...

So probably a kernel/driver issue or hardware problem.


-- 
Regards,
Thomas


_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


  reply	other threads:[~2022-08-02  3:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 16:33 [linux-lvm] lvcreate hangs forever during snapshot creation when suspending volume Thomas Deutschmann
2022-08-01 17:29 ` Zdenek Kabelac
2022-08-01 17:34   ` Zdenek Kabelac
2022-08-01 20:34     ` Thomas Deutschmann
2022-08-02  3:01       ` Thomas Deutschmann [this message]
2022-08-02 14:52         ` Zdenek Kabelac
2022-08-03  1:37           ` Thomas Deutschmann
2022-08-28 22:38             ` Thomas Deutschmann
2022-08-29 10:32               ` Zdenek Kabelac

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='000901d8a61c$3adf2fb0$b09d8f10$@whissi.de' \
    --to=whissi@whissi.de \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).