Sponsored Content
Operating Systems Linux Red Hat device-mapper-multipath path [undef] Post 302345057 by RuBiCK on Tuesday 18th of August 2009 10:10:35 AM
Old 08-18-2009
It's very very strange. I have not found any kind of information about.

Could you post the next?:
lsmod | grep ^dm
uname -a
cat /etc/*release
cat /etc/multipath.conf
 

10 More Discussions You Might Find Interesting

1. HP-UX

Question about the hareware path and device name

# 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)
Discussion started by: bluepluto
1 Replies

2. UNIX for Dummies Questions & Answers

undef

how to undef a readonly parameter? (2 Replies)
Discussion started by: tukuna82
2 Replies

3. Red Hat

Device Mapper Notations and LVM

Hi, I had a doubt regarding device mapper notations and their corresponding LVM volumes. I have configured a volume group with two logical volumes in it as root and swap. The entries in the /etc/fstab file show the dm notations namely, /dev/mapper/VolGroup00-LogVol01... (2 Replies)
Discussion started by: kanna_geekworkz
2 Replies

4. Linux

If i don't have raid disks can i shut down dmraid device-mapper?

hello my centOS newly installed system loading dmraid modules on startup I did remove all LVM/raid things from system installation menus and after installation too but dmraid is still there and he says: no raid disks found also I did modprobe -r dm_raid45 and it do remove it but only until... (7 Replies)
Discussion started by: tip78
7 Replies

5. Red Hat

Ethernet Port device path?

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)
Discussion started by: fedora18
9 Replies

6. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies

7. Red Hat

Raw device/multipath details

Hi, How to find the raw device/multipath details of the LUN used by the diskgroups of the database. file system type -- ASM Oracle -- 11.2.0.3.0 OS -- Linux This is RAC database. Regards, Maddy (2 Replies)
Discussion started by: Maddy123
2 Replies

8. Red Hat

Unable to create customized multipath device

Hi, I am testing on iSCSI + multipath, where i have one iSCSI lun assigned to one server. mpatha (1IET 00010001) dm-2 IET,VIRTUAL-DISK size=100M features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 2:0:0:1 sda 8:0 active ready running `-+-... (6 Replies)
Discussion started by: linux.amrit
6 Replies

9. UNIX for Advanced & Expert Users

Command to see the logical volume path, device mapper path and its corresponding dm device path

Currently I am using this laborious command lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}' Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies

10. Solaris

Creating multipath device with FC Disks

Hello, I am trying to setup a storage server with salvaged equipments: QSSC-S4R server, with QLogic 2562 FC HBA's Clariion KTN-STL4 4GB FC Enclosures Disks Salvaged from EMC Vmax Disks are 520B sector size so i converted to 512B in linux environment and create multipath successfully. But... (4 Replies)
Discussion started by: amd103
4 Replies
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)
All times are GMT -4. The time now is 04:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy