Skip to contentSkip to conversation

Missing VGs?

linux-lvm Brian McCullough 1 participant 2 messages Oct 14, 2006

lore
Share & tools
lore
#0 lore raw

Folks,

I have a drive with two "Linux raid autodetect" partitions, which, as far as I know, have LVM VGs on them.

However, even though mdadm happily starts both RAID devices ( each half of a RAID-1 device ), vgscan and pvscan don't give me answers that I really understand.

First pvscan -vvv ( edited output ):

Processing: pvscan -vvv
O_DIRECT will be used
Setting global/locking_type to 1 Setting global/locking_dir to /var/lock/lvm File-based locking enabled.
Wiping cache of LVM-capable devices
/dev/acpi: Not a block device /dev/adsp: Not a block device
.
.
.
/dev/hda5: No label detected
Closed /dev/hda5
Opened /dev/md5 RO
/dev/md5: size is 78139904 sectors
Closed /dev/md5
/dev/md5: size is 78139904 sectors
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes Closed /dev/md5
Using /dev/md5
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes
/dev/md5: lvm2 label detected
Closed /dev/md5
lvmcache: /dev/md5 now orphaned Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes Closed /dev/md5
Opened /dev/Ubuntu/lv_usrsrc RO
.
.
.
Closed /dev/hda6
lvmcache: /dev/hda6 now in VG Ubuntu Opened /dev/md6 RO
/dev/md6: size is 312576512 sectors
Closed /dev/md6
/dev/md6: size is 312576512 sectors
Opened /dev/md6 RO O_DIRECT /dev/md6: block size is 4096 bytes Closed /dev/md6
Using /dev/md6
Opened /dev/md6 RO O_DIRECT /dev/md6: block size is 4096 bytes
/dev/md6: lvm2 label detected
Closed /dev/md6
lvmcache: /dev/md6 now orphaned Opened /dev/md6 RO O_DIRECT /dev/md6: block size is 4096 bytes Closed /dev/md6
Opened /dev/Ubuntu/lv_home RO
/dev/Ubuntu/lv_home: size is 4710400 sectors
.
.
.
/dev/hda6 9: 3516 62: NULL(0:0)
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes
/dev/md5: lvm2 label detected
Closed /dev/md5
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes Closed /dev/md5
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes
/dev/md5: lvm2 label detected
Closed /dev/md5
Opened /dev/md5 RO O_DIRECT /dev/md5: block size is 4096 bytes Closed /dev/md5
Opened /dev/md6 RO O_DIRECT /dev/md6: block size is 4096 bytes
/dev/md6: lvm2 label detected
Closed /dev/md6
Opened /dev/md6 RO O_DIRECT /dev/md6: block size is 4096 bytes Closed /dev/md6
.
.
.

  PV /dev/hda6   VG Ubuntu        lvm2 [13.98 GB / 2.58 GB free]
  PV /dev/md5                     lvm2 [37.26 GB]
  PV /dev/md6                     lvm2 [149.05 GB]

Total: 7 [372.62 GB] / in use: 5 [186.31 GB] / in no VG: 2 [186.31 GB]

And then, vgscan -vvv said ( also edited ):

Processing: vgscan -vvv
O_DIRECT will be used
Setting global/locking_type to 1
Setting global/locking_dir to /var/lock/lvm
File-based locking enabled.
Wiping cache of LVM-capable devices
/dev/acpi: Not a block device
.
.
.
/dev/hda5: No label detected
Closed /dev/hda5
Opened /dev/md5 RO
/dev/md5: size is 78139904 sectors
Closed /dev/md5
/dev/md5: size is 78139904 sectors
Opened /dev/md5 RO O_DIRECT
/dev/md5: block size is 4096 bytes
Closed /dev/md5
Using /dev/md5
Opened /dev/md5 RO O_DIRECT
/dev/md5: block size is 4096 bytes
/dev/md5: lvm2 label detected
Closed /dev/md5
lvmcache: /dev/md5 now orphaned
Opened /dev/md5 RO O_DIRECT
/dev/md5: block size is 4096 bytes
Closed /dev/md5
Opened /dev/Ubuntu/lv_usrsrc RO
.
.
.
Closed /dev/hda6
lvmcache: /dev/hda6 now in VG Ubuntu
Opened /dev/md6 RO
/dev/md6: size is 312576512 sectors
Closed /dev/md6
/dev/md6: size is 312576512 sectors
Opened /dev/md6 RO O_DIRECT
/dev/md6: block size is 4096 bytes
Closed /dev/md6
Using /dev/md6
Opened /dev/md6 RO O_DIRECT
/dev/md6: block size is 4096 bytes
/dev/md6: lvm2 label detected
Closed /dev/md6
lvmcache: /dev/md6 now orphaned
Opened /dev/md6 RO O_DIRECT
/dev/md6: block size is 4096 bytes
Closed /dev/md6
Opened /dev/Ubuntu/lv_home RO
.
.
.

And nothing more about the supposed VGs on those partitions.

What should I try next?

Thanks,
Brian

#1 lore raw
Quoted 1 line · Brian McCullough

Folks,

And replying to myself:

I then went on to "pvdisplay" and see:

--- NEW Physical volume ---
PV Name /dev/md5
VG Name

  PV Size               37.26 GB
  Allocatable           NO
  PE Size (KByte)       0
  Total PE              0
  Free PE               0
  Allocated PE          0
  PV UUID               62mYb1-sf0O-FA0J-D6TI-kUg6-R5og-mOZAB6

--- NEW Physical volume ---
PV Name /dev/md6
VG Name

  PV Size               149.05 GB
  Allocatable           NO
  PE Size (KByte)       0
  Total PE              0
  Free PE               0
  Allocated PE          0
  PV UUID               uhilT7-33EQ-65Ml-ntFf-iDjJ-fhkn-lag1ev

Am I understanding that "pvcreate" was executed on these two partitions, but not "vgcreate" or "lvcreate".

Thanks,
Brian