Sponsored Content
Full Discussion: Path missing???
Operating Systems AIX Path missing??? Post 302883449 by bakunin on Tuesday 14th of January 2014 08:54:43 AM
Old 01-14-2014
Quote:
Originally Posted by Thala
but why its getting 4paths for an Dual port adapter?
It has nothing to do with how many ports one adapter has. A "path" is just a way of looking at one disk. The short answer is, a "path" is a certain connection from the system to the disk, using a specific way.

Here is the long version: consider the following setup. You have one FC-Adapter (two ports, FCa, FCb), which is connected to two FC-switches (SWa, SWb), which both connect to a storage system. The switches are themselves connected via a crossover-link. You create a single disk on this storage system. This disk will be seen over different paths: FCa-SWa-Disk, FCa-SWa-SWb-Disk, FCb-SWb-Disk, FCb-SWb-SWa-Disk. AIX will therefore create 4 different hdisk-devices when you run cfgmgr.

Now, this is not very comfortable, especially when you create several disks. Each disk will be seen via 4 paths (if you have a fabric more complex than the one i sketched above you might have even more paths) and soon you will have trouble to remember that hdisk137 is in fact hdisk49 and also hdisk87 and hdisk3.

This is where MPIO comes into play: it takes all the hdisk-devices which represent in fact one and only one disk (its like taking a picture of a building from several angles - regardless of how many pictures you take it is always the same one building) and builds a "super-device" above them. You can use this super-device to build VGs, LVs and all other sorts of things you use normally disks for. The MPIO (Multipath-I/O) driver will take care about the relationship of the different hdisk devices and do the bookkeeping for you (and the OS as well).

And there is an additional advantage to it: suppose Switch A in the above picture would fail. Two of the four hdisks (the two paths involving SWa) would be inaccessible, because these pathes would not be usable, but the super-device still works, because it uses ALL paths and if two fail there are still two more to use. In fact this is the main reason one builds such complex fabrics with parallel FC-switches, crossover-links and the like.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

missing Path(in UNIX) when i launch a job on to unix machine using windows SSh

hi i want run an unix application from a windows program/application.i am using SSH(command line version)to log on to a unix machine from windows. the application has to read a configuration file inorder to run. the configuration file .CFG is in bin in my home directory. but the application... (1 Reply)
Discussion started by: megastar
1 Replies

2. Shell Programming and Scripting

Executing Commands From Non-Standard Path (Changing user's PATH secretely???)

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)
Discussion started by: ramesh_samane
2 Replies

3. Shell Programming and Scripting

Retrieve directory path from full file path through sh

Hi, I have a file abcd.txt which has contents in the form of full path file names i.e. $home> vi abcd.txt /a/b/c/r1.txt /q/w/e/r2.txt /z/x/c/r3.txt Now I want to retrieve only the directory path name for each row i.e /a/b/c/ /q/w/e/ How to get the same through shell script?... (7 Replies)
Discussion started by: royzlife
7 Replies

4. SuSE

How to resolve missing missing dependencies with opensuse 11.3 and 12.3?

Hello, This is a programming question as well as a suse question, so let me know if you think I should post this in programming. I have an application that I compiled under opensuse 12.2 using g77-3.3/g++3.3. The program compiles and runs just fine. I gave the application to a colleague who... (2 Replies)
Discussion started by: LMHmedchem
2 Replies

5. Red Hat

Yum - resolving missing dependencies that are not missing

I am trying to install VirtualBox on RHEL 5 but I need the 32 bit version for 32 bit Windows. When I run yum I get the following: sudo yum localinstall /auto/spvtg-it/spvss-migration/Software/VirtualBox-4.3-4.3.2_90405_el6-1.i686.rpm Loaded plugins: fastestmirror Setting up Local Package... (13 Replies)
Discussion started by: gw1500se
13 Replies

6. Shell Programming and Scripting

Moving files from parent path to multiple child path using bash in efficient way

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)
Discussion started by: karthikgv417
6 Replies

7. Shell Programming and Scripting

Generate class path dynamically based on source path

Hi experts, I have multiple file names ending with .jsp located in $SOME_DIR, $SOME_DIR/f1/,$SOME_DIR/f2/test,$SOME_DIR/f3/fa and there are equivalent class files in $SOME_DIR/WEB-INF/classes/_pages,$SOME_DIR/WEB-INF/classes/_pages/_f1,... (0 Replies)
Discussion started by: oraclermanpt
0 Replies

8. 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

9. UNIX for Beginners Questions & Answers

Convert Relative path to Absolute path, without changing directory to the file location.

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

10. Programming

Makefile missing include path Although the path exists and defined

i have make file which i try to make them generic but it keeps to compline it missing include directory this is the makefile : CXX=g++ CPPFAGS= -Wall -O0 -g -std=c++14 INCLUDES = -I/home/vagrant/libuv/include -Isrc LIBS_DIRS = -L/home/vagrant/libuv/build LDFLAGS=... (7 Replies)
Discussion started by: umen
7 Replies
disks(1M)						  System Administration Commands						 disks(1M)

NAME
disks - creates /dev entries for hard disks attached to the system SYNOPSIS
/usr/sbin/disks [-C] [-r rootdir] DESCRIPTION
devfsadm(1M) is now the preferred command for /dev and should be used instead of disks. disks creates symbolic links in the /dev/dsk and /dev/rdsk directories pointing to the actual disk device special files under the /devices directory tree. It performs the following steps: 1. disks searches the kernel device tree to see what hard disks are attached to the system. It notes the /devices pathnames for the slices on the drive and determines the physical component of the corresponding /dev/dsk or /dev/rdsk name. 2. The /dev/dsk and /dev/rdsk directories are checked for disk entries - that is, symbolic links with names of the form cN[tN]dNsN, or cN[tN]dNpN, where N represents a decimal number. cN is the logical controller number, an arbitrary number assigned by this program to designate a particular disk controller. The first controller found on the first occasion this program is run on a system, is assigned number 0. tN is the bus-address number of a subsidiary controller attached to a peripheral bus such as SCSI or IPI (the target number for SCSI, and the facility number for IPI controllers). dN is the number of the disk attached to the controller. sN is the slice number on the disk. pN is the FDISK partition number used by fdisk(1M). (x86 Only) 3. If only some of the disk entries are found in /dev/dsk for a disk that has been found under the /devices directory tree, disks creates the missing symbolic links. If none of the entries for a particular disk are found in /dev/dsk, disks checks to see if any entries exist for other disks attached to the same controller, and if so, creates new entries using the same controller number as used for other disks on the same controller. If no other /dev/dsk entries are found for slices of disks belonging to the same physical con- troller as the current disk, disks assigns the lowest-unused controller number and creates entries for the disk slices using this newly-assigned controller number. disks is run automatically each time a reconfiguration-boot is performed or when add_drv(1M) is executed. When invoking disks(1M) manually, first run drvconfig(1M) to ensure /devices is consistent with the current device configuration. Notice to Driver Writers disks considers all devices with a node type of DDI_NT_BLOCK, DDI_NT_BLOCK_CHAN, DDI_NT_CD, DDI_NT_BLOCK_WWN or DDI_NT_CD_CHAN to be disk devices. disks(1M) requires the minor name of disk devices obey the following format conventions. The minor name for block interfaces consists of a single lowercase ASCII character, a through u. The minor name for character (raw) inter- faces consists of a single lowercase ASCII character, a through u, followed by ,raw. disks translates a through p to s0 through s15, while it translates q through u to p0 through p4. SPARC drivers should only use the first 8 slices: a through h, while x86 drivers can use a through u, with q through u corresponding to fdisk(1M) partitions. q represents the entire disk, while r, s, t, and u represent up to 4 additional partitions. To prevent disks from attempting to automatically generate links for a device, drivers must specify a private node type and refrain from using a node type: DDI_NT_BLOCK, DDI_NT_BLOCK_CHAN, DDI_NT_CD, or DDI_NT_CD_CHAN when calling ddi_create_minor_node(9F). OPTIONS
The following options are supported: -C Causes disks to remove any invalid links after adding any new entries to /dev/dsk and /dev/rdsk. Invalid links are links which refer to non-existent disk nodes that have been removed, powered off, or are otherwise inaccessible. -r rootdir Causes disks to presume that the /dev/dsk, /dev/rdsk and /devices directory trees are found under rootdir, not directly under /. ERRORS
If disks finds entries of a particular logical controller linked to different physical controllers, it prints an error message and exits without making any changes to the /dev directory, since it cannot determine which of the two alternative logical-to-physical mappings is correct. The links should be manually corrected or removed before another reconfiguration-boot is performed. EXAMPLES
Example 1: Creating Block and Character Minor Devices The following example demonstrates creating the block and character minor devices from within the xkdisk driver's attach(9E) function. #include <sys/dkio.h> /* * Create the minor number by combining the instance number * with the slice number. */ #define MINOR_NUM(i, s) ((i) << 4 | (s)) int xkdiskattach(dev_info_t *dip, ddi_attach_cmd_t cmd) { int instance, slice; char name[8]; /* other stuff in attach... */ instance = ddi_get_instance(dip); for (slice = 0; slice < V_NUMPAR; slice++) { /* * create block device interface */ sprintf(name, "%c", slice + 'a'); ddi_create_minor_node(dip, name, S_IFBLK, MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0); /* * create the raw (character) device interface */ sprintf(name,"%c,raw", slice + 'a'); ddi_create_minor_node(dip, name, S_IFCHR, MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0); } } Installing the xkdisk disk driver on a Sun Fire 4800, with the driver controlling a SCSI disk (target 3 attached to an isp(7D) SCSI HBA) and performing a reconfiguration-boot (causing disks to be run) creates the following special files in /devices. # ls -l /devices/ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/ brw-r----- 1 root sys 32, 16 Aug 29 00:02 xkdisk@3,0:a crw-r----- 1 root sys 32, 16 Aug 29 00:02 xkdisk@3,0:a,raw brw-r----- 1 root sys 32, 17 Aug 29 00:02 xkdisk@3,0:b crw-r----- 1 root sys 32, 17 Aug 29 00:02 xkdisk@3,0:b,raw brw-r----- 1 root sys 32, 18 Aug 29 00:02 xkdisk@3,0:c crw-r----- 1 root sys 32, 18 Aug 29 00:02 xkdisk@3,0:c,raw brw-r----- 1 root sys 32, 19 Aug 29 00:02 xkdisk@3,0:d crw-r----- 1 root sys 32, 19 Aug 29 00:02 xkdisk@3,0:d,raw brw-r----- 1 root sys 32, 20 Aug 29 00:02 xkdisk@3,0:e crw-r----- 1 root sys 32, 20 Aug 29 00:02 xkdisk@3,0:e,raw brw-r----- 1 root sys 32, 21 Aug 29 00:02 xkdisk@3,0:f crw-r----- 1 root sys 32, 21 Aug 29 00:02 xkdisk@3,0:f,raw brw-r----- 1 root sys 32, 22 Aug 29 00:02 xkdisk@3,0:g crw-r----- 1 root sys 32, 22 Aug 29 00:02 xkdisk@3,0:g,raw brw-r----- 1 root sys 32, 23 Aug 29 00:02 xkdisk@3,0:h crw-r----- 1 root sys 32, 23 Aug 29 00:02 xkdisk@3,0:h,raw /dev/dsk will contain the disk entries to the block device nodes in /devices # ls -l /dev/dsk /dev/dsk/c0t3d0s0 -> ../../devices/[...]/xkdisk@3,0:a /dev/dsk/c0t3d0s1 -> ../../devices/[...]/xkdisk@3,0:b /dev/dsk/c0t3d0s2 -> ../../devices/[...]/xkdisk@3,0:c /dev/dsk/c0t3d0s3 -> ../../devices/[...]/xkdisk@3,0:d /dev/dsk/c0t3d0s4 -> ../../devices/[...]/xkdisk@3,0:e /dev/dsk/c0t3d0s5 -> ../../devices/[...]/xkdisk@3,0:f /dev/dsk/c0t3d0s6 -> ../../devices/[...]/xkdisk@3,0:g /dev/dsk/c0t3d0s7 -> ../../devices/[...]/xkdisk@3,0:h and /dev/rdsk will contain the disk entries for the character device nodes in /devices # ls -l /dev/rdsk /dev/rdsk/c0t3d0s0 -> ../../devices/[...]/xkdisk@3,0:a,raw /dev/rdsk/c0t3d0s1 -> ../../devices/[...]/xkdisk@3,0:b,raw /dev/rdsk/c0t3d0s2 -> ../../devices/[...]/xkdisk@3,0:c,raw /dev/rdsk/c0t3d0s3 -> ../../devices/[...]/xkdisk@3,0:d,raw /dev/rdsk/c0t3d0s4 -> ../../devices/[...]/xkdisk@3,0:e,raw /dev/rdsk/c0t3d0s5 -> ../../devices/[...]/xkdisk@3,0:f,raw /dev/rdsk/c0t3d0s6 -> ../../devices/[...]/xkdisk@3,0:g,raw /dev/rdsk/c0t3d0s7 -> ../../devices/[...]/xkdisk@3,0:h,raw FILES
/dev/dsk/* Disk entries (block device interface) /dev/rdsk/* Disk entries (character device interface) /devices/* Device special files (minor device nodes) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
add_drv(1M), devfsadm(1M), fdisk(1M), attributes(5), isp(7D), devfs(7FS), dkio(7I), attach(9E), ddi_create_minor_node(9F) Writing Device Drivers BUGS
disks silently ignores malformed minor device names. SunOS 5.10 7 Nov 2002 disks(1M)
All times are GMT -4. The time now is 01:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy