Need help with The LVM devices file

Ask Fedora
,
1

I’ve been fighting to get my f38 system up to fedora 40 or 41 and i can’t get my old lvm volume recognised, I didn’t have an lvm devices file so i created one as per the instruction here but at boot i Still need to runvg vgchange -ay to access the data, how can i make it so that vgchange -ay step is no longer neeeded?

2

I have been using LVM for many years, and have never needed to create nor modify a system devices file.

The man page for vgchange shows

OPTIONS

       -a|--activate y|n|ay
              Change  the  active  state  of LVs.  An active LV can be used through a block device, allowing data on the LV to be accessed.  y
              makes LVs active, or available.  n makes LVs inactive, or unavailable.  The block device for the LV is added or removed from the
              system using device-mapper in the kernel.  A symbolic link /dev/VGName/LVName pointing to the device node is also added/removed.
              All software and scripts should access the device through the symbolic link and present this as the name of the device.  The lo‐
              cation and name of the underlying device node may depend on the distribution, configuration (e.g. udev), or release version.  ay
              specifies autoactivation, which is used by system-generated activation commands. By default, LVs are autoactivated.  An  autoac‐
              tivation  property can be set on a VG or LV to disable autoactivation, see --setautoactivation y|n in vgchange, lvchange, vgcre‐
              ate, and lvcreate.  Display the property with vgs or lvs "-o autoactivation".  The lvm.conf(5)  auto_activation_volume_list  in‐
              cludes  names  of  VGs  or  LVs  that  should be autoactivated, and anything not listed is not autoactivated.  When auto_activa‐
              tion_volume_list is undefined (the default), it has no effect.  If auto_activation_volume_list is defined and empty, no LVs  are
              autoactivated.   Items included by auto_activation_volume_list will not be autoactivated if the autoactivation property has been
              disabled.  See lvmlockd(8) for more information about activation options ey and sy for shared VGs.
3

back in f 38 days i needed to enable scan_lvs = 1 because I used a mirrored cache on nvme to speed up my spinning rust, that allows LVM LVs to be used as PVs, the annoying thing is lack of any feedback, i get no errors