All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Corbin <dcorbin@machturtle.com>
To: LVM <linux-lvm@sistina.com>
Subject: [linux-lvm] RAID+LVM
Date: Sun Nov 24 06:58:02 2002	[thread overview]
Message-ID: <3DE0CCBB.3010405@machturtle.com> (raw)

I have a debian system with LVM on top of a RAID.  Once up and running, 
it seems to work OK.  It's the getting it up and running that's a 
problem.  At boot, the raid drive is started, and then

                /sbin/vgscan --verbose >/root/vg.start
                /sbin/vgchange -a y --verbose >>/root/vg.start

This yields :
----vg.start----
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

vgchange -- locking logical volume manager
vgchange -- finding all volume group(s)
vgchange -- no volume groups found
----end----

Now, after the system finishes booting, if login as root and run those 
two commands again, I get.


----vg.start----
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- reading data of volume group "vg0" from physical volume(s)
vgscan -- found inactive volume group "vg0"
vgscan -- getting block device numbers for logical volumes

vgscan -- checking block device numbers of logical volumes

vgscan -- inserting "vg0" into lvmtab
vgscan -- backing up volume group "vg0"
vgscan -- checking volume group name "vg0"
vgscan -- checking volume group consistency of "vg0"
vgscan -- checking existence of "/etc/lvmtab.d"
vgscan -- storing volume group data of "vg0" in "/etc/lvmtab.d/vg0.tmp"
vgscan -- storing physical volume data of "vg0" in "/etc/lvmtab.d/vg0.tmp"
vgscan -- storing logical volume data of volume group "vg0" in 
"/etc/lvmtab.d/vg0.tmp"
vgscan -- renaming "/etc/lvmtab.d/vg0.tmp" to "/etc/lvmtab.d/vg0"
vgscan -- removing special files and directory for volume group "vg0"
vgscan -- creating directory and group character special file for "vg0"
vgscan -- creating block device special files for vg0
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

vgchange -- locking logical volume manager
vgchange -- finding all volume group(s)
vgchange -- checking volume group name "vg0"
vgchange -- checking existence of volume group "vg0"
vgchange -- reading volume group data for "vg0" from lvmtab
vgchange -- checking volume group consistency  of "vg0"
vgchange -- checking if all physical volumes of volume group "vg0" are 
available
vgchange -- creating VGDA for "vg0" in kernel
vgchange -- volume group "vg0" successfully activated

vgchange -- unlocking logical volume manager
----end----

and everything works.

Now, maybe this is a question better asked on the RAID list, but what's 
changing between the boot-time process  and later that suddenly makes 
the LVM stuff work?

David Corbin.

             reply	other threads:[~2002-11-24  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24  6:58 David Corbin [this message]
2002-11-24 18:30 ` [linux-lvm] RAID+LVM Jose Luis Domingo Lopez
2002-11-24 18:51   ` David Corbin
  -- strict thread matches above, loose matches on Subject: below --
2002-06-25 10:05 [linux-lvm] RAID & LVM Info - Demerson
2002-06-25 11:16 ` Svetoslav Slavtchev
2002-06-25 11:19 ` William Blunn
2002-06-26  5:45   ` Heinz J . Mauelshagen
2002-06-26  9:29     ` James Hawtin
2002-06-26 10:35       ` Heinz J . Mauelshagen
2000-05-10 23:37 [linux-lvm] raid " Jeffrey E. Mast
2000-05-11  0:02 ` Michael Marxmeier

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=3DE0CCBB.3010405@machturtle.com \
    --to=dcorbin@machturtle.com \
    --cc=linux-lvm@sistina.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 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.