From: "Jason A. Fager" <jafager@jafager.com>
To: Linux-LVM@sistina.com
Subject: [linux-lvm] vgscan fails to find volume groups
Date: Wed Apr 17 02:38:02 2002 [thread overview]
Message-ID: <20020417075302.GB26644@codegate.jafager.com> (raw)
I have been attempting to get LVM set up on a freshly-installed
Slackware 8.0 system (custom 2.4.18 monolithic kernel, LVM 1.0.3,
no kernel patches). It works fine in multi-user mode, it works
fine in single-user mode, however I set up the single-user init
script like this:
(/ is mounted read only at this point)
mount -o remount,rw /
vgscan
vgchange -a y
mount -o remount,ro /
(stock Slackware fsck and mount bits)
The only volume group I have contains one physical volume
(/dev/sdb, on an Adaptec 7xxx controller). For some reason,
vgscan doesn't pick up the volume group. The exit code is 0,
and looking at the debug output it hits /dev/sdb and spits out
the same messages as when it hits all the other devices.
As an experiment I put a call to sulogin before the vgscan and
tried running it by hand; same thing happened. I tried running
pvcreate (on the whole disk, and after creating an LVM partition
/dev/sdb1) and it failed with error code 7.
As another experiment, I tried setting up a loopback filesystem
on a file in the root directory. That worked perfectly; vgscan
picked it up, vgchange activated it, and the rest of the init
script ran fsck and mounted it. Other than setting up the
loopback file the only thing I did was add a call to losetup
before the vgscan.
Not sure if this is a problem with the kernel (i.e. SCSI driver)
or a problem with LVM, or some boneheaded thing I'm doing wrong.
Any advice you can give would be appreciated -- let me know if
I can provide more information.
thanks,
jafager
next reply other threads:[~2002-04-17 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 2:38 Jason A. Fager [this message]
2002-04-17 8:29 ` [linux-lvm] vgscan fails to find volume groups AJ Lewis
2002-04-17 10:50 ` 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=20020417075302.GB26644@codegate.jafager.com \
--to=jafager@jafager.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.