kpartx(8) [linux man page]
KPARTX(8) Linux Administrator's Manual KPARTX(8) NAME
kpartx - Create device maps from partition tables SYNOPSIS
kpartx [-a | -d | -l] [-v] wholedisk DESCRIPTION
This tool, derived from util-linux' partx, reads partition tables on specified device and create device maps over partitions segments detected. It is called from hotplug upon device maps creation and deletion. OPTIONS
-a Add partition mappings -r Readonly partition mappings -r Read-only partition mappings -d Delete partition mappings -u Update partition mappings -l List partition mappings that would be added -a -p set device name-partition number delimiter -f force creation of mappings; overrides 'no_partitions' feature -g force GUID partition table (GPT) -v Operate verbosely -s Sync mode. Don't return until the partitions are created EXAMPLE
To mount all the partitions in a raw disk image: kpartx -av disk.img This will output lines such as: loop3p1 : 0 20964762 /dev/loop3 63 The loop3p1 is the name of a device file under /dev/mapper which you can use to access the partition, for example to fsck it: fsck /dev/mapper/loop3p1 When you're done, you need to remove the devices: kpartx -d disk.img SEE ALSO
multipath(8) multipathd(8) hotplug(8) AUTHORS
This man page was assembled By Patrick Caulfield for the Debian project. From documentation provided by the multipath author Christophe Varoqui, <christophe.varoqui@opensvc.com> and others. July 2006 KPARTX(8)
Check Out this Related Man Page
MULTIPATH(8) Linux Administrator's Manual MULTIPATH(8) NAME
multipath - Device mapper target autoconfig SYNOPSIS
multipath [-v verbosity] [-d] [-h|-l|-ll|-f|-t|-F-B] [-p failover|multibus|group_by_serial|group_by_prio|group_by_node_name] [device] DESCRIPTION
multipath is used to detect multiple paths to devices for fail-over or performance reasons and coalesces them OPTIONS
-v level verbosity, print all paths and multipaths 0 no output 1 print the created or updated multipath names only, for use to feed other tools like kpartx 2 + print all info : detected paths, coalesced paths (ie multipaths) and device maps -h print usage text -d dry run, do not create or update devmaps -l show the current multipath topology from information fetched in sysfs and the device mapper -ll show the current multipath topology from all available information (sysfs, the device mapper, path checkers ...) -f flush a multipath device map specified as parameter, if unused -F flush all unused multipath device maps -t print internal hardware table to stdout -r force devmap reload -B treat the bindings file as read only -p policy force new maps to use the specified policy: failover 1 path per priority group multibus all paths in 1 priority group group_by_serial 1 priority group per serial group_by_prio 1 priority group per priority value. Priorities are determined by callout programs specified as a global, per-con- troller or per-multipath option in the configuration file group_by_node_name 1 priority group per target node name. Target node names are fetched in /sys/class/fc_transport/target*/node_name. Existing maps are not modified. device update only the devmap the path pointed by device is in. device is in the /dev/sdb (as shown by udev in the $DEVNAME variable) or major:minor format. device may alternatively be a multipath mapname SEE ALSO
multipathd(8), multipath.conf(5), kpartx(8), udev(8), dmsetup(8) hotplug(8) AUTHORS
multipath was developed by Christophe Varoqui, <christophe.varoqui@opensvc.com> and others. July 2006 MULTIPATH(8)