From: Tom Yan <tom.ty89@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Problem with pvscan --cache -aay $pv (lvm2-pvscan@.service) on raid type LV
Date: Mon, 28 Jun 2021 16:58:57 +0800 [thread overview]
Message-ID: <CAGnHSEkfvZEaU_tWz0si3cD3gYwiXRT3-ijM7kMsNuWp=_UHoQ@mail.gmail.com> (raw)
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
[tom@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@archlinux ~]$ sudo pvscan --cache -aay /dev/sda2
pvscan[5800] PV /dev/sda2 online, VG green is complete.
pvscan[5800] VG green skip autoactivation.
[tom@archlinux ~]$ sudo pvscan --cache -aay /dev/sdb
pvscan[5802] PV /dev/sdb online, VG green is complete.
pvscan[5802] VG green skip autoactivation.
[tom@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@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@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
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
reply other threads:[~2021-06-28 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGnHSEkfvZEaU_tWz0si3cD3gYwiXRT3-ijM7kMsNuWp=_UHoQ@mail.gmail.com' \
--to=tom.ty89@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).