You are not logged in.

#1 2024-03-20 12:14:08

tormoz
Member
Registered: 2020-06-22
Posts: 2

lvm volumes partially initialized (or not) after reboot.

my setup looks like this:

# lsblk
NAME                           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda                              8:0    0   1.8T  0 disk
├─sda1                           8:1    0     1G  0 part  /boot
└─sda2                           8:2    0   1.8T  0 part
  └─fast                       254:2    0   1.8T  0 crypt
    └─arch_new-root_corig      254:5    0   1.6T  0 lvm
      └─arch_new-root          254:6    0   1.6T  0 lvm   /
sdb                              8:16   0 465.8G  0 disk
└─ssd-sata                     254:1    0 465.7G  0 crypt
  ├─arch_new-cache_cpool_cdata 254:3    0   100G  0 lvm
  │ └─arch_new-root            254:6    0   1.6T  0 lvm   /
  ├─arch_new-cache_cpool_cmeta 254:4    0    12M  0 lvm
  │ └─arch_new-root            254:6    0   1.6T  0 lvm   /
  └─arch_new-swap              254:7    0   200G  0 lvm   [SWAP]
sdc                              8:32   0   1.8T  0 disk
└─slow                         254:0    0   1.8T  0 crypt
  ├─arch_new-thin_tmeta        254:8    0   108M  0 lvm
  │ └─arch_new-thin            254:10   0   1.6T  0 lvm
  └─arch_new-thin_tdata        254:9    0   1.6T  0 lvm
    └─arch_new-thin            254:10   0   1.6T  0 lvm

However after reboot arch_new-thin is not fully activated (and some times even root-cache is broken). My investigations led me to this post which i don't want to resurrect without good reason. I believe that initrd (i use systemd initrd) really kills vgchange in mid-state and leaves thin volume half-activated. To reactivate it you need to deactivate tdata and tmeta parts first which complicates things.

Mar 20 14:09:22 archlinux systemd[1]: Started /usr/bin/lvm vgchange -aay --autoactivation event arch_new.
Mar 20 14:09:22 archlinux lvm[1069]: TRANSACTION_ID=0
Mar 20 14:09:22 archlinux lvm[1069]: METADATA_FREE_BLOCKS=27533
Mar 20 14:09:22 archlinux lvm[1069]: Checking thin metadata
Mar 20 14:09:22 archlinux lvm[1069]: device details tree
Mar 20 14:09:22 archlinux lvm[1069]: mapping tree
Mar 20 14:09:22 archlinux lvm[1028]:   wait4 child process 1069 failed: Interrupted system call
Mar 20 14:09:22 archlinux lvm[1028]:   Check of pool arch_new/thin failed (status:-1). Manual repair required!
Mar 20 14:09:22 archlinux lvm[1028]:   device-mapper: remove ioctl on  (254:8) failed: Device or resource busy
Mar 20 14:09:22 archlinux lvm[1028]:   Interrupted...
Mar 20 14:09:22 archlinux lvm[1028]:   2 logical volume(s) in volume group "arch_new" now active
Mar 20 14:09:22 archlinux systemd[1]: Stopping /usr/bin/lvm vgchange -aay --autoactivation event arch_new...
Mar 20 14:09:22 archlinux systemd[1]: lvm-activate-arch_new.service: Main process exited, code=exited, status=5/NOTINSTALLED
Mar 20 14:09:22 archlinux systemd[1]: lvm-activate-arch_new.service: Failed with result 'exit-code'.
Mar 20 14:09:22 archlinux systemd[1]: Stopped /usr/bin/lvm vgchange -aay --autoactivation event arch_new.

Is it my misconfiguration or should i post a bug and where? systemd? lvm? thin-provisioning?

Last edited by tormoz (2024-03-20 23:44:32)

Offline

#2 2026-08-31 21:56:55

idlmn
Member
Registered: 2026-08-31
Posts: 1

Re: lvm volumes partially initialized (or not) after reboot.

I have the exact same error. With systemd in the HOOKS array of my mkinitcpio.conf the error occurs. When i replace systemd with udev, the system boots without any problems.

NAME                     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                        8:0    0 465,8G  0 disk 
└─sda1                     8:1    0 465,8G  0 part 
  ├─vg0-lv_root          253:0    0    48G  0 lvm  /
  ├─vg0-lv_vm_arch-real  253:1    0    48G  1 lvm  
  │ └─vg0-lv_vm_arch     253:2    0    48G  1 lvm  
  └─vg0-lv_vm_win11-real 253:3    0   130G  1 lvm  
    └─vg0-lv_vm_win11    253:4    0   130G  1 lvm  
sdb                        8:16   0 931,5G  0 disk 
├─sdb1                     8:17   0   510G  0 part 
└─sdb2                     8:18   0   420G  0 part 
  ├─vg0-lv_tpool0_tmeta  253:5    0    76M  0 lvm  
  └─vg0-lv_tpool0_tdata  253:6    0   150G  0 lvm  
nvme0n1                  259:0    0 232,9G  0 disk 
└─nvme0n1p1              259:1    0 232,9G  0 part 
  └─vg1-lv_games         253:7    0   432G  0 lvm  /storage/0
nvme1n1                  259:2    0 465,8G  0 disk 
├─nvme1n1p1              259:3    0   500M  0 part /boot/efi
├─nvme1n1p2              259:4    0    16M  0 part 
├─nvme1n1p3              259:5    0  64,2G  0 part 
├─nvme1n1p4              259:6    0   813M  0 part 
├─nvme1n1p5              259:7    0   200G  0 part 
└─nvme1n1p6              259:8    0   200G  0 part 
  └─vg1-lv_games         253:7    0   432G  0 lvm  /storage/0
Aug 31 23:24:30 archlinux lvm[285]: PV /dev/sda1 online, VG vg0 incomplete (need 1).
Aug 31 23:24:30 archlinux lvm[295]: PV /dev/nvme1n1p6 online, VG vg1 incomplete (need 1).
Aug 31 23:24:30 archlinux lvm[296]: PV /dev/nvme0n1p1 online, VG vg1 is complete.
Aug 31 23:24:30 archlinux lvm[303]: PV /dev/sdb2 online, VG vg0 is complete.
Aug 31 23:24:30 archlinux systemd[1]: Started [systemd-run] /usr/bin/lvm vgchange -aay --autoactivation event vg0.
Aug 31 23:24:31 archlinux systemd[1]: Started [systemd-run] /usr/bin/lvm vgchange -aay --autoactivation event vg1.
Aug 31 23:24:31 archlinux lvm[348]:   1 logical volume(s) in volume group "vg1" now active
Aug 31 23:24:31 archlinux systemd[1]: lvm-activate-vg1.service: Deactivated successfully.
Aug 31 23:24:32 archlinux lvm[309]:   wait4 child process 362 failed: Interrupted system call.
Aug 31 23:24:32 archlinux lvm[309]:   Check of pool vg0/lv_tpool0 failed (status:-1). Manual repair required!
Aug 31 23:24:32 archlinux lvm[309]:   device-mapper: remove ioctl on vg0-lv_tpool0_tmeta (253:5) failed: Device or resource busy
Aug 31 23:24:32 archlinux lvm[309]:   Interrupted...
Aug 31 23:24:32 archlinux lvm[309]:   3 logical volume(s) in volume group "vg0" now active
Aug 31 23:24:32 archlinux systemd[1]: Stopping [systemd-run] /usr/bin/lvm vgchange -aay --autoactivation event vg0...
Aug 31 23:24:32 archlinux systemd[1]: lvm-activate-vg0.service: Main process exited, code=exited, status=5/NOTINSTALLED
Aug 31 23:24:32 archlinux systemd[1]: lvm-activate-vg0.service: Failed with result 'exit-code'.
Aug 31 23:24:32 archlinux systemd[1]: Stopped [systemd-run] /usr/bin/lvm vgchange -aay --autoactivation event vg0.
Aug 31 23:24:33 pc-arch lvm[462]:   1 logical volume(s) in volume group "vg1" monitored
Aug 31 23:24:33 pc-arch lvm[462]:   5 logical volume(s) in volume group "vg0" monitored
Aug 31 23:24:34 pc-arch lvm[585]: PV /dev/nvme1n1p6 online, VG vg1 is complete.
Aug 31 23:24:34 pc-arch lvm[585]: VG vg1 finished
Aug 31 23:24:34 pc-arch lvm[589]: PV /dev/nvme0n1p1 online, VG vg1 is complete.
Aug 31 23:24:34 pc-arch lvm[589]: VG vg1 finished
Aug 31 23:24:34 pc-arch lvm[596]: PV /dev/sda1 online, VG vg0 is complete.
Aug 31 23:24:34 pc-arch lvm[596]: VG vg0 finished
Aug 31 23:24:34 pc-arch lvm[607]: PV /dev/sdb2 online, VG vg0 is complete.
Aug 31 23:24:34 pc-arch lvm[607]: VG vg0 finished

Offline

Board footer

Powered by FluxBB