From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] upgrade to rh7.3 broke lvm
Date: Mon Jul 22 06:13:02 2002 [thread overview]
Message-ID: <20020722130252.B23420@sistina.com> (raw)
In-Reply-To: <3D358A8D.27A77928@mooncrest.net>; from yossi@Mooncrest.Net on Wed, Jul 17, 2002 at 05:17:33PM +0200
Yossi,
the upgrade should have brought you compatible user space and kernel LVM parts.
Can you find your VG(s) running vgdisplay?
/dev/mg0 is no valid logical volume name to be use for mounting.
Must be something like /dev/YourVGName/YourLVName.
On Wed, Jul 17, 2002 at 05:17:33PM +0200, Yossi wrote:
> Upgraded from RH7.1 to RH7.3. The 7.1 was built with the lvm patch to
> the kernel. The 7.3 RH kernel has lvm built in. After the upgrade, I
> receive the message "/dev/mg0 not a block device" when I try to mount
> it. I tried exporting the vg and importing it without errors but it
> still doesn't mount. I suspect that this may be due to different
> versions of the kernel part of the lvm versus the usermode parts of lvm.
>
> Thanks for any help,
>
> L. Baker
> MVS, Ltd.
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-07-22 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 10:11 [linux-lvm] upgrade to rh7.3 broke lvm Yossi
2002-07-22 6:13 ` Heinz J . Mauelshagen [this message]
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=20020722130252.B23420@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox