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

Re: [linux-lvm] vgscan -f created duplicate block devices


with devfs in place, you need to run vgscan _before_ "vgchange -ay" is run
in your system startup script (whatever that is distro-depenedent).

vgscan works on all volume groups (no matter if active or not).

On Mon, May 26, 2003 at 03:23:56AM -0700, Ellis Whitehead wrote:
> Hi Heinz,
> > have you removed _all_ /dev/-Entries for LVs and retried 
> > "vgscan -f" without success so far ?
> I'm using devfs, and removal of the /dev/{VG}/{LV} entries isn't permitted.  The
> VG and LVs show up under /dev if the VG is active, and otherwise they aren't
> present.  Once the VG is active, the LV entries cannot be modified by the usual
> command line tools, as far as I've seen...
> Since vgscan can only works on active volumes, and since active volumes are
> already immutably set in /dev, I'm afraid this solution won't work.
> Is there any way to manually set the block device?  Or is there any way to get
> vgscan to start anew without the block device numbers in /dev?
> Thanks!
> Ellis
> _______________________________________________
> linux-lvm mailing list
> linux-lvm sistina com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***


Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
Mauelshagen Sistina com                           +49 2626 141200
                                                       FAX 924446

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