Arch Linux

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)