I am running RHEL6 on a physical node (HP Proliant).
If it normal for the root device to get listed in the "multipath -ll" output? (Listed below as dm-4, HP LOGICAL VOLUME).
Hello everybody...
I have a Server conected to a Disk Array through 2 canals of FiberChannel... I've installed RedHat Advance Server 3 and of course i see two device files that refer the same disk: for example: /dev/sda and /dev/sdb are refered to the same Lun... This is the same case for a new... (2 Replies)
I don't undestand how to combine 4 nics in order to use DM Multipath. Do I have to install each nic with its IP address? If yes, do I need a group IP address? This concept is not clear for me.
The connection beetwen the server (DELL Poweredge T710) and the SAN through iscsi works well, I used... (1 Reply)
hi all,
there´s one thing i dont understand ...
in the file /etc/multipath.conf, why do we incluide "dm-" ??? a device mapper dm- is not supposed to be a multipath part that will be used after configuring mutipath dm??
devnode_blacklist {
devnode... (0 Replies)
Hi All,
When I execute multipath -ll command that time display only 3 path (mpath1,mpath2 and mpath5), not display other 2 path (mpath3 and mpath4). I have configure 5 path in /etc/multipath.conf file. What is the reason behind it. Please help me.
Please find below the output :
... (5 Replies)
Hi All,
When I execute "multipath -ll" command that time display only 3 path (orafra2,oradata2 and oradata1), not display other 2 path (orafra1 and data1). I have configure 5 path in "/etc/multipath.conf" file. What is the reason behind it. Please help me.
Please find below some output for... (4 Replies)
Hello,
i have a problem with the multipath tools configuration.
i can't remove the local disk paths.
the multipath.conf archives configuration is:
---------------------------------------------------------
$ cat /etc/multipath.conf
blacklist{
devnode cciss
devnode fd
... (0 Replies)
Hi,
My HP machine is using as boot device a disk defined in the Storage (IBM V5000). The connection is done by fiber connected through fiber switch.
No lacal disks are installed.
I'm using redhat 6.6.
I've installed and configured multipath.
Everything seems to work properly, however,... (0 Replies)
Discussion started by: Pazzeo
0 Replies
LEARN ABOUT OPENSOLARIS
di_path_client_devfs_path
di_devfs_path(3DEVINFO) Device Information Library Functions di_devfs_path(3DEVINFO)NAME
di_devfs_path, di_devfs_minor_path, di_path_devfs_path, di_path_client_devfs_path, di_devfs_path_free - generate and free path names
SYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ]
#include <libdevinfo.h>
char *di_devfs_path(di_node_t node);
char *di_devfs_minor_path(di_minor_t minor);
char *di_path_devfs_path(di_path_t path);
char *di_path_client_devfs_path(di_path_t path);
void di_devfs_path_free(char *path_buf);
PARAMETERS
node The handle to a device node in a di_init(3DEVINFO) snapshot.
minor The handle to a device minor node in a snapshot.
path The handle to a device path node in a snapshot.
path_buf A pointer returned by di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), or di_path_client_devfs_path().
DESCRIPTION
The di_devfs_path() function generates the physical path of the device node specified by node.
The di_devfs_minor_path() function generates the physical path of the device minor node specified by minor.
The di_path_devfs_path() function generates the pHCI physical path to the device associated with the specified path node. The returned
string is identical to the di_devfs_path() for the device had the device not been supported by multipath.
The di_path_client_devfs_path() function generates the vHCI physical path of the multipath client device node associated with the device
identity of the specified path node. The returned string is identical to the di_devfs_path() of the multipath client device node.
The di_devfs_path_free() function frees memory that was allocated to store the path returned by di_devfs_path(), di_devfs_minor_path(),
di_path_devfs_path(), and di_path_client_devfs_path(). The caller is responsible for freeing this memory by calling di_devfs_path_free().
RETURN VALUES
Upon successful completion, the di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions
return a pointer to the string containing the path to a device node, a device minor node, or a device path node, respectively. Otherwise,
they return NULL and errno is set to indicate the error. For a non-NULL return, the path will not have a "/devices" prefix.
ERRORS
The di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions will fail if:
EINVAL The node, minor, or path argument is not a valid handle.
The di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions can also return any error value
returned by malloc(3C).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO di_init(3DEVINFO), libdevinfo(3LIB), malloc(3C), attributes(5)
Writing Device Drivers
SunOS 5.11 15 May 2008 di_devfs_path(3DEVINFO)