From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Changing device numbers.
Date: Tue, 13 Mar 2001 14:37:06 -0700 (MST) [thread overview]
Message-ID: <200103132137.f2DLb6o05452@webber.adilger.int> (raw)
In-Reply-To: <005801c0ac4b$a781cc00$0f01a8c0@myplace.net> from Bas at "Mar 13, 2001 09:57:29 pm"
Bas writes:
> Rerunning lilo seemed to work, but I had the same problem just a while ago
> without changing anything but adding a LV.
Maybe because you are running "vgscan" on each boot? It is not really
needed by LVM unless the disk configuration changes. When you run it,
there is the possibility of the VG and LV devices changing major numbers.
Even so, it is a problem (IMHO) that LVM likes to delete all of the
device files each time vgscan is run. The correct thing to do would
be to have "pvscan" create a file of UUID->disk mappings on each boot,
and leave the LVM devices alone. Then vgscan would only be needed if
there is a major disaster.
Another possibility is to use the "UUID root" patch, which can locate
the root filesystem at mount time by the ext2 UUID or LABEL. I don't
think it is ported to 2.4 yet.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-13 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 4:48 [linux-lvm] Changing device numbers Bas
2001-03-13 20:17 ` Wichert Akkerman
2001-03-14 5:24 ` Bas
2001-03-13 20:43 ` Wichert Akkerman
2001-03-14 5:52 ` Bas
2001-03-13 21:41 ` Luca Berra
2001-03-13 20:44 ` Terje Kvernes
2001-03-14 5:57 ` Bas
2001-03-13 21:37 ` Andreas Dilger [this message]
2001-03-14 16:37 ` Heinz J. Mauelshagen
2001-03-15 4:11 ` Bas
2001-03-14 20:47 ` Heinz J. Mauelshagen
2001-03-15 5:29 ` Bas
2001-03-13 20:55 ` Andreas Dilger
2001-03-14 6:13 ` Bas
2001-03-13 21:41 ` Andreas Dilger
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=200103132137.f2DLb6o05452@webber.adilger.int \
--to=adilger@turbolinux.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;
as well as URLs for NNTP newsgroup(s).