From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] HELP: vgscan segfaults
Date: Thu Jan 30 03:35:02 2003 [thread overview]
Message-ID: <20030130103301.C26745@sistina.com> (raw)
In-Reply-To: <20030129160958.GG802@tykepenguin.com>; from caulfield@sistina.com on Wed, Jan 29, 2003 at 04:09:58PM +0000
On Wed, Jan 29, 2003 at 04:09:58PM +0000, Patrick Caulfield wrote:
> On Wed, Jan 29, 2003 at 04:59:36PM +0100, Peter Lohmann wrote:
> > >
> > > If your metadata backups are up-to-date then "vgchange -ay" should activate the
> > > volumes regardless. Something must have changed, programs don't just work one
> > > day and segv the next without good reason.
> >
> > I know... but still:
> >
> > --> vgchange -ay myvg
> > vgchange -- volume group "myvg" does not exist
> >
> > Same with vgchange -ay
> >
> > :-(
>
> Looks like the segfaulting vgscan started to write the metadata backups. See of
> you can find valid ones in /etc/lvmtab and restore them using vgcfgrestore.
>
> OR it might be as easy as creating a new /etc/lvmtab with "myvg\0" in it and
> retrying vgchange.
...plus "mkdir /etc/lvmtab.d;cp /etc/lvmconf/myvg.conf /etc/lvmtab.d/myvg"
before the "vgchange -ay".
Additionally you need to change the LVM config (i.e. by running
"lvchange -pr .." or something) so that the ondisk metadata gets written
back to the PVs.
> --
>
> patrick
>
>
> _______________________________________________
> 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/
--
Regards,
Heinz -- The LVM Guy --
*** 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-01-30 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 9:13 [linux-lvm] HELP: vgscan segfaults Peter Lohmann
2003-01-29 9:19 ` Patrick Caulfield
2003-01-29 9:33 ` Peter Lohmann
2003-01-29 9:43 ` Patrick Caulfield
2003-01-29 10:00 ` Peter Lohmann
2003-01-29 10:10 ` Patrick Caulfield
2003-01-30 3:35 ` Heinz J . Mauelshagen [this message]
2003-02-04 8:06 ` [linux-lvm] lvm and fai Sébastien GALLET
2003-02-04 8:26 ` Patrick Caulfield
2003-02-26 8:17 ` [linux-lvm] HELP: vgscan segfaults Terje Kvernes
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=20030130103301.C26745@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.