Attachment 1859037 Details for Bug 1985288 – Reproducer

Reproducer

BUG (text/plain), 1.35 KB, created by Marius Vollmer on 2022-02-04 12:12:20 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marius Vollmer

Created: 2022-02-04 12:12:20 UTC

Size: 1.35 KB

patch

obsolete

>#! /bin/sh
>
>set -ex
>
># Make a fresh block device
>dd if=/dev/zero of=/disk.img bs=1M count=500
>DEV=$(losetup -f --show /disk.img)
>
># Put a volume group on it with one logical volume that doesn't use
># all of it yet.
>vgcreate vgroup0 $DEV
>lvcreate vgroup0 -n lvol0 -L 250M
>
># Create a LUKS container and a filesystem
>echo einszweidrei | cryptsetup luksFormat /dev/vgroup0/lvol0
>echo einszweidrei | cryptsetup open /dev/vgroup0/lvol0 luks0
>mkfs.xfs /dev/mapper/luks0 -m uuid=face850a-3294-4b47-a391-33b3f8dbdf71
>
># Mount the lot via fstab so that systemd is taking interest
>echo >>/etc/fstab "UUID=face850a-3294-4b47-a391-33b3f8dbdf71 /mnt auto defaults 0 0"
>systemctl daemon-reload
>mount /mnt
>
># This shows that it is mounted
>findmnt /mnt
>
># Make the logical volume bigger
>lvresize vgroup0/lvol0 -L+100M
>
># Now grow the LUKS container.  This will suspend luks0 and sometimes
># there is a uevent while it is suspended, which will cause systemd to
># think that luks0 has disappeared, and to unmount it.
>echo einszweidrei | cryptsetup resize /dev/mapper/luks0 --device-size 300M
>
># This is how to reproduce the bug reliably:
># dmsetup suspend /dev/mapper/luks0
># udevadm trigger
># udevadm settle
># dmsetup resume /dev/mapper/luks0
>
># This shows that it is no longer mounted
>findmnt /mnt || true
>
># Clean up
>umount /mnt || true
>cryptsetup close luks0
>vgremove -f vgroup0
>losetup -d $DEV

Actions: View

Attachments on bug 1985288: 1859037