[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] Root on LVM and vgscan

I have root running on lvm on sw raid partitions on linux 2.2.18.  It all
works fine.  However I have had difficulty during booting after adding new
LVs.  The symptom is that the initial mounts of LVs fails or the wrong
partition is mounted.

What happens is that vgscan is run during the initrd phase and so the lvmtab
is updated on the ram disk.  Once the root file system on the hard disk has
been mounted the lvmtab on that comes into use.  That has not been updated by
vgscan and so does not reflect the changes. 

Obviously it's possible to run vgscan again (between remounting root rw and
checking the other discs) to update the lvmtab but it does beg a few

1) why does mount use the data in lvmtab and not in /proc to find out about
   active VGs?

2) if lvmtab is so essetial why is it not updated by vgcreate/lvcreate and
   other utilities when changes are made?

3) would it not be possible/better to update lvmtab from /proc without doing
   a rescan.

I don't know the issues involved and reasoning behind the design of this
aspect of LVM but it does seem to me that there is something less than ideal
in the current scheme.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]