[linux-lvm] Problem with pvscan --cache -aay $pv (lvm2-pvscan at .service) on raid type LV

[Tom Yan]

Hi,

I notice that `pvscan --cache -aay $pv` will not activate LV(s) of
raid type even when all of its/their legs are up. Only `pvscan --cache
-aay` (without a PV specified) will activate such LV(s). Is it some
kind of bug / regression?

[tom at archlinux ~]$ sudo lvchange -an /dev/green/meh
[tom at archlinux ~]$ sudo lvs green/meh
  LV   VG    Attr       LSize   Pool Origin Data%  Meta%  Move Log
Cpy%Sync Convert
  meh  green rwi---r--- 512.00m
[tom at archlinux ~]$ sudo pvscan --cache -aay /dev/sda2
  pvscan[5800] PV /dev/sda2 online, VG green is complete.
  pvscan[5800] VG green skip autoactivation.
[tom at archlinux ~]$ sudo pvscan --cache -aay /dev/sdb
  pvscan[5802] PV /dev/sdb online, VG green is complete.
  pvscan[5802] VG green skip autoactivation.
[tom at archlinux ~]$ sudo lvs green/meh
  LV   VG    Attr       LSize   Pool Origin Data%  Meta%  Move Log
Cpy%Sync Convert
  meh  green rwi---r--- 512.00m
[tom at archlinux ~]$ sudo pvscan --cache -aay
  pvscan[5806] PV /dev/sda2 online, VG green incomplete (need 1).
  pvscan[5806] PV /dev/sdb online, VG green is complete.
  pvscan[5806] VG green run autoactivation.
  5 logical volume(s) in volume group "green" now active
[tom at archlinux ~]$ sudo lvs green/meh
  LV   VG    Attr       LSize   Pool Origin Data%  Meta%  Move Log
Cpy%Sync Convert
  meh  green rwi-a-r--- 512.00m
100.00

What I expect is that, if the command is run on any of the legs, such
LV will be activated as long as all of the legs are up.

Regards,
Tom