From: Dick Middleton <dick@lingbrae.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Upgrade Linux 2.2 to 2.4 problems
Date: Wed Oct 2 07:01:01 2002 [thread overview]
Message-ID: <3D9ADFF2.4080606@lingbrae.com> (raw)
In-Reply-To: 20021002122716.B1955@sistina.com
Heinz,
>this can't be the exact LVM 0.9-Beta7 error message.
>
It sure is (except error is written ERROR and the message is on 2 lines
:-) )
>Is /proc really mounted, *before* vgchange runs in /linuxrc?
>
Hmm - I'm not sure how I can tell. The mount command certainly comes first
and there are no visible error messages. I'm just using
lvmcreate_initrd. If the
mount command fails then it gives an error message and vgchange gives me
different error messages so I assume it's working.
>BTW: why do you use such an old kernel and LVM version?
> Please give a recent one and LVM 1.0.5 a try.
>
That's what I was trying to do (for a while) until I discovered this
kernel only has beta7 in it.
Curiously I had more success with 1.0.5 tools on this kernel.
I think I'll take your advice and start again.
Many thanks for your support.
Dick
>>
>>vgscan appears to work ok but vgchange fails with:
>>
>>Error- can't get names of physical volumes - please check if /proc is
>>mounted.
>>
>>Well, /proc is mounted - in fact if it isn't mounted I don't this error.
>>
>>What does this error message mean and what's likely to be wrong to cause it?
>>
>>
>
>
>
prev parent reply other threads:[~2002-10-02 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 17:23 [linux-lvm] Upgrade Linux 2.2 to 2.4 problems Dick Middleton
2002-10-02 5:28 ` Heinz J . Mauelshagen
2002-10-02 7:01 ` Dick Middleton [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=3D9ADFF2.4080606@lingbrae.com \
--to=dick@lingbrae.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