| Message ID | 20250128071609.676581-1-hch@lst.de (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | common: skip tests using LVM when the device is no known | expand |
On Tue, Jan 28, 2025 at 08:16:05AM +0100, Christoph Hellwig wrote: > LVM has a lot of elaborate code to make the users life painful. This > includes claiming the device type is unknown if it doesn't match it's > elaborately crafted internal list instead of just letting the user use > it. Skip tests using LVM if this is the case to avoid arcane failures > due to missing lvm devices when using null_blk. > > Signed-off-by: Christoph Hellwig <hch@lst.de> > --- > tests/generic/081 | 6 +++++- > tests/generic/108 | 6 +++++- > tests/generic/459 | 6 +++++- > 3 files changed, 15 insertions(+), 3 deletions(-) > > diff --git a/tests/generic/081 b/tests/generic/081 > index 37137d937b05..97928bf4a435 100755 > --- a/tests/generic/081 > +++ b/tests/generic/081 > @@ -66,7 +66,11 @@ lvsize=$((size * 85 / 100)) # ~256M > # make sure there's enough disk space for 256M lv, test for 300M here in case > # lvm uses some space for metadata > _scratch_mkfs_sized $((size * 1024 * 1024)) >>$seqres.full 2>&1 > -$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 > + > +# lvm has a hardcoded list of valid devices and fails with > +# "device type is unknown" for those not in the list like null_blk > +$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 || \ > + _notrun "LVM is too stupid for this device" Should this get turned into a common helper? _require_lvm_support() { local bdev="$1" $LVM_PROG pvcreate --test "$bdev" || \ _notrun "$bdev: cannot use lvm here" } I guess the downside is that pvcreate on my system (Debian 12) will trip over any existing disk label and ask if you want to wipe it. If you say no then it returns nonzero, and if you say yes then it goes into an infinite loop. You can of course $WIPEFS_PROG -a $bdev but ugghh. --D > # We use yes pipe instead of 'lvcreate --yes' because old version of lvm > # (like 2.02.95 in RHEL6) don't support --yes option > yes | $LVM_PROG lvcreate -L ${lvsize}M -n $lvname $vgname >>$seqres.full 2>&1 > diff --git a/tests/generic/108 b/tests/generic/108 > index f630450ec66d..4f86ec946511 100755 > --- a/tests/generic/108 > +++ b/tests/generic/108 > @@ -51,7 +51,11 @@ test -b "$SCSI_DEBUG_DEV" || _notrun "Failed to initialize scsi debug device" > echo "SCSI debug device $SCSI_DEBUG_DEV" >>$seqres.full > > # create striped volume with 4MB stripe size > -$LVM_PROG pvcreate -f $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 > +# > +# lvm has a hardcoded list of valid devices and fails with > +# "device type is unknown" for those not in the list like null_blk > +$LVM_PROG pvcreate -f $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 || \ > + _notrun "LVM is too stupid for this device" > $LVM_PROG vgcreate -f $vgname $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 > # We use yes pipe instead of 'lvcreate --yes' because old version of lvm > # (like 2.02.95 in RHEL6) don't support --yes option > diff --git a/tests/generic/459 b/tests/generic/459 > index 40c87e20f8b9..3f5f0f2b7dc1 100755 > --- a/tests/generic/459 > +++ b/tests/generic/459 > @@ -84,7 +84,11 @@ is_shutdown_or_ro() > _scratch_mkfs_sized $((350 * 1024 * 1024)) >>$seqres.full 2>&1 > > # Create a 200MB dm-thin POOL > -$LVM_PROG pvcreate -f $SCRATCH_DEV >>$seqres.full 2>&1 > +# > +# lvm has a hardcoded list of valid devices and fails with > +# "device type is unknown" for those not in the list like null_blk > +$LVM_PROG pvcreate -f $SCRATCH_DEV >>$seqres.full 2>&1 || \ > + _notrun "LVM is too stupid for this device" > $LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 > > $LVM_PROG lvcreate --thinpool $poolname --errorwhenfull y \ > -- > 2.45.2 > >
On Tue, Jan 28, 2025 at 11:31:22AM -0800, Darrick J. Wong wrote: > Should this get turned into a common helper? > I guess the downside is that pvcreate on my system (Debian 12) will trip > over any existing disk label and ask if you want to wipe it. If you say > no then it returns nonzero, and if you say yes then it goes into an > infinite loop. > > You can of course $WIPEFS_PROG -a $bdev but ugghh. Honestly, for now I just want to avoid the tests failing due to lvm stupidity. If someone has the time to do something more elaborate (I don't right now), the proper thing is to stop using lvm and replace it with something less stupid. That might be direct use of dm, or simulating failures with null_blk or scsi_debug.
On Wed, Jan 29, 2025 at 06:24:43AM +0100, Christoph Hellwig wrote: > On Tue, Jan 28, 2025 at 11:31:22AM -0800, Darrick J. Wong wrote: > > Should this get turned into a common helper? > > > I guess the downside is that pvcreate on my system (Debian 12) will trip > > over any existing disk label and ask if you want to wipe it. If you say > > no then it returns nonzero, and if you say yes then it goes into an > > infinite loop. > > > > You can of course $WIPEFS_PROG -a $bdev but ugghh. > > Honestly, for now I just want to avoid the tests failing due to lvm > stupidity. If someone has the time to do something more elaborate > (I don't right now), the proper thing is to stop using lvm and replace > it with something less stupid. That might be direct use of dm, > or simulating failures with null_blk or scsi_debug. Eh, I'm not that into a weird wipefs and pvcreate --test. If someone feels so motivated to test that on a bunch of distros they can do that refactoring. I already have too many patches stuck in djwong-dev. Reviewed-by: "Darrick J. Wong" <djwong@kernel.org> --D
diff --git a/tests/generic/081 b/tests/generic/081 index 37137d937b05..97928bf4a435 100755 --- a/tests/generic/081 +++ b/tests/generic/081 @@ -66,7 +66,11 @@ lvsize=$((size * 85 / 100)) # ~256M # make sure there's enough disk space for 256M lv, test for 300M here in case # lvm uses some space for metadata _scratch_mkfs_sized $((size * 1024 * 1024)) >>$seqres.full 2>&1 -$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 + +# lvm has a hardcoded list of valid devices and fails with +# "device type is unknown" for those not in the list like null_blk +$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 || \ + _notrun "LVM is too stupid for this device" # We use yes pipe instead of 'lvcreate --yes' because old version of lvm # (like 2.02.95 in RHEL6) don't support --yes option yes | $LVM_PROG lvcreate -L ${lvsize}M -n $lvname $vgname >>$seqres.full 2>&1 diff --git a/tests/generic/108 b/tests/generic/108 index f630450ec66d..4f86ec946511 100755 --- a/tests/generic/108 +++ b/tests/generic/108 @@ -51,7 +51,11 @@ test -b "$SCSI_DEBUG_DEV" || _notrun "Failed to initialize scsi debug device" echo "SCSI debug device $SCSI_DEBUG_DEV" >>$seqres.full # create striped volume with 4MB stripe size -$LVM_PROG pvcreate -f $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 +# +# lvm has a hardcoded list of valid devices and fails with +# "device type is unknown" for those not in the list like null_blk +$LVM_PROG pvcreate -f $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 || \ + _notrun "LVM is too stupid for this device" $LVM_PROG vgcreate -f $vgname $SCSI_DEBUG_DEV $SCRATCH_DEV >>$seqres.full 2>&1 # We use yes pipe instead of 'lvcreate --yes' because old version of lvm # (like 2.02.95 in RHEL6) don't support --yes option diff --git a/tests/generic/459 b/tests/generic/459 index 40c87e20f8b9..3f5f0f2b7dc1 100755 --- a/tests/generic/459 +++ b/tests/generic/459 @@ -84,7 +84,11 @@ is_shutdown_or_ro() _scratch_mkfs_sized $((350 * 1024 * 1024)) >>$seqres.full 2>&1 # Create a 200MB dm-thin POOL -$LVM_PROG pvcreate -f $SCRATCH_DEV >>$seqres.full 2>&1 +# +# lvm has a hardcoded list of valid devices and fails with +# "device type is unknown" for those not in the list like null_blk +$LVM_PROG pvcreate -f $SCRATCH_DEV >>$seqres.full 2>&1 || \ + _notrun "LVM is too stupid for this device" $LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 $LVM_PROG lvcreate --thinpool $poolname --errorwhenfull y \
LVM has a lot of elaborate code to make the users life painful. This includes claiming the device type is unknown if it doesn't match it's elaborately crafted internal list instead of just letting the user use it. Skip tests using LVM if this is the case to avoid arcane failures due to missing lvm devices when using null_blk. Signed-off-by: Christoph Hellwig <hch@lst.de> --- tests/generic/081 | 6 +++++- tests/generic/108 | 6 +++++- tests/generic/459 | 6 +++++- 3 files changed, 15 insertions(+), 3 deletions(-)