On 02/24/2014 01:40 PM, Oliver Rath wrote: > Hi Peter! > > Am 24.02.2014 09:41, schrieb Peter Rajnoha: >> On 02/23/2014 11:36 PM, Oliver Rath wrote: >> The parted itself creates a new device-mapper mapping that represents >> the partition. Then it's like any other device-mapper device and so >> the /dev content is created by 10-dm-disk.rules (the /dev/mapper >> content) and 13-dm-disk.rules (the /dev/disk content). Parted has this >> functionality integrated so there's no need to call kpartx in addition. > > On my machine parted-2.3 was running. Upgrading to parted-3.1 didnt > help, BUT building parted-3.1 for myself with ./configure > --disable-device-mapper works! Then parted does his job without creating > these deices implicitly. Yes, I was just about to write that :) I think there's no option in parted to avoid creating these mappings for partitions once the parted is compiled with device-mapper support. So yes, the only option is either to recompile without devmapper support or always remove these mappings manually... > > Maybe you know a less radical method? I.e. I could exclude some names in > lvm.conf or something like this? The names of the lvm whould should > create subvolumes are well defined. You would need to tell parted to stop syncing the state after partition signatures are created/removed on/from disk. But parted always creates/removes the partition mappings unconditionally (...or it calls BLKRRPART/blkpg for non-dm devices). You can try using fdisk instead which does not do this step and requires calling partprobe or kpartx manually after partitioning. -- Peter _______________________________________________ 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/
