Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dm(4) [netbsd man page]

DM(4)							   BSD Kernel Interfaces Manual 						     DM(4)

dm -- Device-mapper disk driver SYNOPSIS
pseudo-device dm DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping. This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con- figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD. Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin- ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only. In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file: pseudo-device dm #device-mapper disk device dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for such a line is: 0 10240 linear /dev/wd1a 384 dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target, there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second parameter is the offset on this disk from the start of the disk/partition. SEE ALSO
config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8) HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0. AUTHORS
Adam Hamsik <> implemented the device-mapper driver for NetBSD. Brett Lymn <>, Reinoud Zandijk <>, and Bill Stouder-Studenmund <> provided guidance and answered questions about the NetBSD implementation. BUGS
This driver is still work-in-progress--there can be bugs. BSD
August 30, 2008 BSD

Check Out this Related Man Page

MKNOD(8)						    BSD System Manager's Manual 						  MKNOD(8)

mknod -- make device special file SYNOPSIS
mknod [-F format] name [c | b] major minor mknod [-F format] name [c | b] major unit subunit mknod name [c | b] number mknod name w DESCRIPTION
The mknod command creates device special files. To make nodes manually, the required arguments are: name Device name, for example ``sd'' for a SCSI disk on an HP300 or a ``pty'' for pseudo-devices. b | c | w Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the type is b. Whiteout nodes are type w. All other devices are character type devices, such as terminal and pseudo devices, and are type c. major The major device number is an integer number which tells the kernel which device driver entry point to use. minor The minor device number tells the kernel which one of several similar devices the node corresponds to; for example, it may be a spe- cific serial port or pty. unit and subunit The unit and subunit numbers select a subset of a device; for example, the unit may specify a particular SCSI disk, and the subunit a partition on that disk. (Currently this form of specification is only supported by the bsdos format, for compatibility with the BSD/OS mknod(8).) Device numbers for different operating systems may be packed in a different format. To create device nodes that may be used by such an oper- ating system (e.g. in an exported file system used for netbooting), the -F option is used. The following formats are recognized: native, 386bsd, 4bsd, bsdos, freebsd, hpux, isc, linux, netbsd, osf1, sco, solaris, sunos, svr3, svr4 and ultrix. Alternatively, a single opaque device number may be specified. SEE ALSO
mkfifo(1), mkfifo(2), mknod(2) HISTORY
A mknod command appeared in Version 6 AT&T UNIX. The -F option appeared in NetBSD 1.4. NetBSD 1.4 September 11, 1998 NetBSD 1.4
Man Page