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@archlinux ~]$ sudo lvchange -an /dev/green/meh
Well, it doesn't really change the game:
[root@archlinux ~]# rm /run/lvm/pvs_online/*
[root@archlinux ~]# lvs | grep meh
mehgreen rwi---r--- 512.00m
[root@archlinux ~]# pvscan --cache -aay 8\:2
pvscan[36958] PV /dev/sda2 online, VG green incomplete (need 1).
[root@archlinux ~]# pvscan
On Sun, Jun 27, 2021 at 09:01:43PM +0800, Tom Yan wrote:
> [tom@archlinux ~]$ sudo pvscan --cache -aay /dev/sdb
> pvscan[2066] PV /dev/sdb online, VG green is complete.
> pvscan[2066] VG green skip autoactivation.
The "skip autoactivation" means that the VG has already been activated
by a
Hi again,
I just noticed that, `pvscan --cache -aay $device` does work as
expected if I remove `/run/lvm/vgs_online/green`. I still couldn't
figure out why it doesn't work on boot though. (I do notice that Arch
by default uses the "legacy" way (run the pvscan commands with a udev
rule RUN
Hi again(x2),
Never mind, I figured it out:
https://bugs.archlinux.org/task/71385
Sorry for the noise.
Regards,
Tom
On Tue, 29 Jun 2021 at 01:25, Tom Yan wrote:
>
> Hi again,
>
> I just noticed that, `pvscan --cache -aay $device` does work as
> expected if I remove
Il 2021-06-28 05:28 Stuart D Gathman ha scritto:
Yes. I like the checksums in metadata feature for enhanced integrity
checking.
Until recently btrfs has issue when a LVM snapshot was mounted. It is
now solved?
It seems too complicated to have anytime soon - but when a filesystem
detects
