linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@bdmcc-us.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Missing VGs?
Date: Sat, 14 Oct 2006 14:26:19 -0400	[thread overview]
Message-ID: <20061014182619.GA25852@bdmcc-us.com> (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

             reply	other threads:[~2006-10-14 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14 18:26 Brian McCullough [this message]
2006-10-14 18:44 ` [linux-lvm] Missing VGs? Brian McCullough
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17 22:13 Brian McCullough

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=20061014182619.GA25852@bdmcc-us.com \
    --to=bdmc@bdmcc-us.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 NNTP newsgroup(s).