[linux-lvm] LVM partition and lvm commands in initrd
markryde at gmail.com
Sat Sep 23 12:35:08 UTC 2006
>...that the mkinitrd/mkinitramfs-script will sniff around your system...
>to boot a system that
> doesn't have LVM
Luca said in an answer to this message: "LVM is much more than a
It is clear to me that the mkinitrd is dependant upon what I install.
But it is not clear to me what in the installation of Fedora Core
system as having LVM (or not having LVM).
What is a system that does have an LVM and a system that does NOT
have LVM ?
Suppose somebody goes to an unknown fedora machine and want to know if there
is LVM on that machine. How can he know it? is the existence of LVM
a precondition ? meaning, if he runs "fdisk -l |grep LVM" and doesn't
get anything than it is not LVM , and if there is an LVM partition
than it is LVM machine? or is it not enough to to this check and there
should be some another check ?
The thing is that I made 2 installations of Fedora Core 5; in the
first I chose to format a partition as LVM and in the second I did
not. Is this is what causes the initrd to have the lvm commands in the
first case and not to have them in the second place ?
because I don't remeber that elsewhere in the installation process
that I did select
connected with LVM (there is ofcouse the manual layout in which I
chode /dev/VolumeGroup... in the first case).
On 9/23/06, Aleksandr Koltsoff <czr at iki.fi> wrote:
> Mark Ryden wrote:
> > Hello linux-lvm,
> > There is one point which I want to understand and I hope I can get
> > help here.
> initrds are created automatically for you upon kernel package
> installation in most linux distributions (fedora included). this means
> that the mkinitrd/mkinitramfs-script will sniff around your system and
> decide which modules (dm, ext3, hba-drivers, etc) to include in the
> initrd and also sometimes decide which scripts to call (vgscan and
> friends) and whether to include lvm-related tools into the initrd.
> Similar story for software raid.
> This means that if you take the initrd and try to boot a system that
> doesn't have LVM you're doing something wrong. initrds are not supposed
> to be portable, however this will of course depend very much on the
> Hope this answers your question.
> linux-lvm mailing list
> linux-lvm at redhat.com
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
More information about the linux-lvm