From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] undocumented strange LVM behaviour
Date: Wed Nov 27 16:10:02 2002 [thread overview]
Message-ID: <20021127230241.A3406@sistina.com> (raw)
In-Reply-To: <E18H7Ca-0006IL-00@mail.kellnerweg.de>; from daniel@kellnerweg.de on Wed, Nov 27, 2002 at 07:43:46PM +0100
On Wed, Nov 27, 2002 at 07:43:46PM +0100, Daniel Zeiss wrote:
> vgcfgrestore be an option to restore my lvm?
No, this looks like a strange /proc/partitions problem (LVM tries to retrieve
device pathes from there and obviously fails on that).
Does "cat /proc/partitions" show any strangenesses ?
Regards,
Heinz -- The LVM Guy --
>
>
> Daniel Zeiss wrote:
>
> > Hello,
> >
> > my lvm (2 partitions on 2 discs /dev/hde4 /devhdg2) on a Debian Woody
> > Linux (2.4.18-686) shows some strange behaviour:
> >
> > After rebooting my computer, vgscan found an inactive "vg01" to be my
> > volume group but vgchange -a y said:
> >
> > vgchange -- ERROR: can't get name(s) of physical volumes
> > vgchange -- Please check, if /proc is mounted
> >
> > my /proc is mounted and in /proc/lvm /global is says:
> >
> > Total: 0 VGs 0 PVs 0 LVs (LVs open)
> > Global: 152 bytes malloced IOP version 10 0:05:06 active
> >
> > I do _not_ use devfs, /dev is complete and working.
> >
> > My lvm are just my home dirs, so uncomming them in /etc/fstabs and
> > rebooting brings my system up with kde now problem and root can log in
> > and work (which it shouldnt do with kde, just testing).
> >
> > My / is on /dev/hde3, so it isnt a disc failure.
> >
> > the output of
> >
> > vgchange -a y -d
> >
> > is attached.
> >
> > What can I do to get my LVM up running _without_ dataloss?
> >
> > Thank you
> >
> > Daniel
> >
> >
>
>
> _______________________________________________
> 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:[~2002-11-27 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 6:39 [linux-lvm] undocumented strange LVM behaviour Daniel Zeiss
2002-11-27 12:46 ` Daniel Zeiss
2002-11-27 16:10 ` Heinz J . Mauelshagen [this message]
2002-11-27 23:59 ` Daniel Zeiss
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=20021127230241.A3406@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.