All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] question about vg underlying pv devs order
@ 2020-05-27  4:51 heming.zhao
  0 siblings, 0 replies; only message in thread
From: heming.zhao @ 2020-05-27  4:51 UTC (permalink / raw)
  To: linux-lvm

Hello list,

one our customer reported a issue. After executing lvextend, the vg underlying pv devs changed.

I do a summary from my watching.

first, pv devies in /etc/lvm/backup/systemvg & /etc/lvm/archive/systemvg-xxx are correct.

but using pvdissect (url: https://wiki.syslinux.org/wiki/index.php?title=Development/LVM_support/pvdissect), the script dumped show pv related device had been changed after executing lvextend command.

the part output of pvdissect like:
```
0x00006000 (metadata.value):
systemvg {
     id = "id-xxx"
     seqno = 11
     format = "lvm2"
     status = ["RESIZEABLE", "READ", "WRITE"]
     flags = []
     extent_size = 8192
     max_lv = 0
     max_pv = 0
     metadata_copies = 0

     physical_volumes {

         pv0 {
             id = "pv0-uuid-xxxx"  <=== it didn't change
             device = "/dev/sdb"   <=== it changed to /dev/sda

             status = ["ALLOCATABLE"]
             flags = []
             dev_size = 4806528
             pe_start = 2048
             pe_count = 586
         }

         pv1 {
             id = "pv1-uuid-xxxx"   <=== it didn't change
             device = "/dev/sdc"    <=== it changed to /dev/sdb

             status = ["ALLOCATABLE"]
             flags = []
             dev_size = 4806528
             pe_start = 2048
             pe_count = 586
         }

         pv2 {
             id = "pv2-uuid-xxxx"    <=== it didn't change
             device = "/dev/sdd"     <=== it changed to /dev/sdc

             status = ["ALLOCATABLE"]
             flags = []
             dev_size = 4806528
             pe_start = 2048
             pe_count = 586
         }

     ... ... # other parts are correct
```

(the systemvg consists of many LVs, ie: usrlv, varlv, optlv, homelv.)
  

my question:
the devs order changed, but after system reboot, everything work fine. why?

I not very familiar with lvm code.
 From my watching, it looks lvm uses pv uuid not device to work, is it right?

Thanks.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-05-27  5:32 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-27  4:51 [linux-lvm] question about vg underlying pv devs order heming.zhao

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.