Command to see the logical volume path, device mapper path and its corresponding dm device path
Currently I am using this laborious command
Would like to know if there is any shorter method to get this mapping of combined output (lvpath, /dev/mapper/ and /dev/dm/* ), possibly a single command.
hi. Im trying to install a switch.
And the manual says i should type a command including a SerialPortDevicePath. which is the filepath to serial port used for connection.
However.. nothing about how to find this info.
Could anyone help me where to find this path?
thx
mr.T (6 Replies)
# ioscan -f | grep disk
Class I H/W Path Driver S/W State H/W Type Description
disk 3 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC ... (1 Reply)
Hy
I have several logical volumes that are turned into raw devices used by Informix DB. I would like to add some more.
In /dev directory i see logical volumes as block files: lv_name1, lv_name2 ...
and
i see raw devices defined as character files:
rlv_name1, rlv_name2 ...
As i see,... (5 Replies)
Hi:
I have a requirement as below:
I have some standard Unix commands modified and kept them in a directory say /usr/clsh/bin. For example I have a script named "ls" kept here which is modified version of "ls" (say it always gives long listing i.e. ls -l).
When any user logs on and types... (2 Replies)
I have an HP blade with Qlogic HBA's connected to an EVA8000. I have downloaded the latest multipath.conf from HP's website. The drive presented to the server appears to be configured and working except the output of "multipath -l" shows for all paths. What is causing this output?
mpath0... (2 Replies)
Hello friends,
I am building one driver related to wifi. When I am looking its hex dump, I can see that it is including a path to one particular file of kernel headers. It is as under.
6C 75 65 2E 0A 00 00 00 25 64 2E 25 64 2E 25 64 lue.....%d.%d.%d
2D 25 73 00 00 00 00 00 42 45... (4 Replies)
After we upgraded one PW450 machine from (networker 7.2 & solaris 9) to (networker 7.4 and solaris 10) through scratch installation
Only one of two HP tape drives is shown in inquire command
And we are getting strange logs in messages file (attached)
For 2nd drive 1cbn character specific file... (4 Replies)
Hi,
I have a server program that reads data coming in on USB ports. Device paths are in the format: /dev/ttyUSB0
Now, I would like to log data from another device coming in over Ethernet. My first step is trying to track down what the correct device path is which I am unsure of.
Anyone... (9 Replies)
Hi All,
Can you please provide some pointers to move files from Base path to multiple paths in efficient way.Folder Structure is already created.
/Path/AdminUser/User1/1111/Reports/aaa.txt to /Path/User1/1111/Reports/aaa.txt
/Path/AdminUser/User1/2222/Reports/bbb.txt to... (6 Replies)
Hello,
I am creating a file with all the source folders included in my git branch, when i grep for the used source, i found source included as relative path instead of absolute path, how can convert relative path to absolute path without changing directory to that folder and using readlink -f ? ... (4 Replies)
Discussion started by: Sekhar419
4 Replies
LEARN ABOUT NETBSD
dm
DM(4) BSD Kernel Interfaces Manual DM(4)NAME
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 <haad@NetBSD.org> implemented the device-mapper driver for NetBSD.
Brett Lymn <blymn@NetBSD.org>,
Reinoud Zandijk <reinoud@NetBSD.org>, and
Bill Stouder-Studenmund <wrstuden@NetBSD.org> 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