From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Accessing LVM partitions from a rescue system
Date: Tue Nov 26 05:32:02 2002 [thread overview]
Message-ID: <20021126122431.B28853@sistina.com> (raw)
In-Reply-To: <200211251722.31489.pantaleimon@home.no>; from pantaleimon@home.no on Mon, Nov 25, 2002 at 05:22:31PM +0100
On Mon, Nov 25, 2002 at 05:22:31PM +0100, Pantaleimon wrote:
> On Monday 25 November 2002 15:17, Heinz J . Mauelshagen wrote:
> > Yeah, pretty strange...
> >
> > Forgot to ask: you run the _very_ same (LVM) versions on the rescue media
> > too ?
> >
> > Regards,
> > Heinz -- The LVM Guy --
>
> Yes, I berlieve I run the same versions on both occasions. I have only one
> file called lvm-mod.o on my system and that's the one I copied to use with
> the rescue system. I couldn't figure out how to get the version no. from the
> module file, though, just to make sure it's really the same. Tried "insmod
> --verbose" but it didn't give any version no.
You can look the LVM version up in /proc/lvm/global.
>
> On the other hand, your question made me check the kernelversion etc. for the
> rescue system, and it turns out the rescue disk is based on SuSE 5.3 (while I
> use 7.3) and uses libc5 according to the documentation. That sounds like
> something to do with libraries (even to those not yet initiated, like me,
> into the inner secrets of Linux :-) ). When I have mounted my normal root
> drive on /mnt in the rescue system I link /mnt/lib/* from /lib to be able to
> run the lvm programs. But that only adds the libraries from /mnt/lib. It
> doesn't replace those already there with identical names, if any. Do you
> think the reason could be a mix up of libraries from different versions? Just
> a theory.
Having a more recent one for the rescue media is a good idea.
But it could be a trivial thing like not having all device nodes
on the rescue media. In particular /dev/hda16.
Regards,
Heinz -- The LVM Guy --
>
>
> > > > > - Anders
> > > > >
> > > > > > Hello
> > > > > >
> > > > > > I am trying to mount my LVM partitions manually after booting into
> > > > > > a rescue system from floppies. I am not able to do this. During a
> > > > > > normal boot from my harddisk LVM works just fine. Notice the output
> > > > > > from pvscan and lvmdiskscan below. I ran those commands first from
> > > > > > the rescue system and then from a normally booted system. In the
> > > > > > rescue system /dev/hda16 is not there. I don't know if that is
> > > > > > related to my problem, though.
> > > > > >
> > > > > > Here are the details of what I am doing:
> > > > > >
> > > > > > Setup:
> > > > > >
> > > > > > boot partition /dev/hda2 type Linux with Ext2
> > > >
> > > > <SNIP>
> > > >
> > > > > > lvmdiskscan -- 28 partitions
> > > > > > lvmdiskscan -- 20 LVM physical volume partitions
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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/
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >-=-
> >
> > _______________________________________________
> > 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/
>
>
> _______________________________________________
> 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-26 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:22 [linux-lvm] Accessing LVM partitions from a rescue system Pantaleimon
2002-11-26 5:32 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-24 15:08 Pantaleimon
2002-11-24 18:40 ` Anders Widman
2002-11-25 3:06 ` Pantaleimon
2002-11-25 4:40 ` Heinz J . Mauelshagen
2002-11-25 8:00 ` Pantaleimon
2002-11-25 8:25 ` Heinz J . Mauelshagen
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=20021126122431.B28853@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