From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgcfgrestore and bootstrap
Date: Wed Sep 24 03:49:02 2003 [thread overview]
Message-ID: <20030924103749.C2618@sistina.com> (raw)
In-Reply-To: <200309231754.20420.gingiabios@email.it>; from gingiabios@email.it on Tue, Sep 23, 2003 at 05:54:20PM +0200
Gingia,
the normal procedure is "vgscan ; vgchange -ay ; mount -a"
rather than vgcfgrestore before vgchange.
vgscan recognizes changes in the IO configuration (e.g. devices moved
to different addresses causing device nodes t change).
Have you tried "vgscan ; vgchange -ay ; mount -a" before ?
(keep in mind, that vgscan needs space below /etc/ to store metadata copies)
Regards,
Heinz -- The LVM Guy --
On Tue, Sep 23, 2003 at 05:54:20PM +0200, Gingia wrote:
> Hi all.
> I write in this list to explain the problem with the meta data and the
> inconsistence.
>
> Thank to Heinz J . Mauelshagen i solve the principal problem.
>
> Now i have another problem caused by the same root.
>
> When i start the devlopment server (debian woody), it remain in the runlevel
> 1 e ask me the pass to root access for device-filesystem problem.
> It said that it had problem with the lvm.
>
> To start the sewrver i must to :
> 1) vgcfgrestore -n volume1 -f /etc/lvmconf/volume1.conf /dev/i2o/hda3
> 2) vgchange -a y
> 3) mount -a
> and only now i can go to runlevel 2 for normal start.
>
> So i understand that 1) the "restoring" metadata is a routine operation at
> boostrap instead of a propely restoring 2) for some reason this does not
> happen more.
>
> So my question is: Why ?
> How i can restabilished this at boot time? I can move to solve this other
> problem?
> Can you help me?
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-09-24 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 11:03 [linux-lvm] vgcfgrestore and bootstrap Gingia
2003-09-24 3:49 ` Heinz J . Mauelshagen [this message]
2003-09-24 7:23 ` Gingia
2003-09-24 7:59 ` Heinz J . Mauelshagen
2003-09-25 4:36 ` Gingia
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=20030924103749.C2618@sistina.com \
--to=mauelshagen@sistina.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.