Re: device mapper Q

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

 



On Fri, Nov 19, 2004 at 08:33:19PM +0100, Dieter Stueken wrote:
> Q: For any reason I'm missing
> one of these link. Should I create it by hand?

vgmknodes fixes things

Boot-up scripts should include vgscan --mknodes.

LVM2 will be updated at some point to recognise /dev/mapper/vg-lv
names on the command line, but it doesn't yet - you must always
use vg/lv.

dm-<minor_number> in sysfs/block is something I have no time for
but seems pretty harmless.

But /dev/dm* sounds quite unnecessary.

devfs puts things into /dev/mapper automatically: udev should
be configured to do the same - but it seems it can't because
that would mean userspace call outs running scripts at critical 
times when they are not permitted to block (e.g. must not allocate 
any memory) or else could lock up the whole machine.
So everything should use libdevmapper (or equivalent), often
via dmsetup, to keep /dev/mapper up-to-date.

Alasdair
-- 
agk@redhat.com

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux