All of lore.kernel.org
 help / color / mirror / Atom feed
From: lvm@interlinx.bc.ca
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] moving single LVM disk from one system to another
Date: Mon Aug 19 04:03:01 2002	[thread overview]
Message-ID: <20020819090226.GA13367@linux.interlinx.bc.ca> (raw)
In-Reply-To: <20020819102427.A24314@sistina.com>

On Mon, Aug 19, 2002 at 10:24:27AM +0200, Heinz J . Mauelshagen wrote:
> 
> Is that with our without devfs?

Interesting you should ask.  :-)

> Have you checked, that device nodes are in your initrd for vgscan to be able
> to access them fine?

I am/was (for the past hour or two) just hunting this possibility
down.  I have the system currently booting from a tftp server (via an
etherboot diskette) so that I can shorten the cycle of "modify initrd
with more debugging and re-test".  I am just about to put some
debugging into the native hard disk booting initrd to see what disk
nodes are there and such.

The kernel is being booted with "devfs=mount", so they should be
there.  I should know in a few more minutes what is going on.

> Does vgscan fail finding your VG our is it just wrong entries in /etc/fstab
> failing your root mount?

vgscan fails to find the VG.  I am sure this is going to turn out to
be missing device nodes, but will have figure out why that is if devfs
is being mounted.

Will keep ya posted.

b.

-- 
Brian J. Murrell

  reply	other threads:[~2002-08-19  4:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17  2:10 [linux-lvm] moving single LVM disk from one system to another lvm
2002-08-17  5:50 ` Goetz Bock
2002-08-17  9:19   ` lvm
2002-08-19  3:39 ` Heinz J . Mauelshagen
2002-08-19  4:03   ` lvm [this message]
2002-08-19  5:05     ` lvm
2002-08-19  7:24       ` lvm
2002-08-19  7:31         ` 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=20020819090226.GA13367@linux.interlinx.bc.ca \
    --to=lvm@interlinx.bc.ca \
    --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.