05-02-2007
The vpaths you are reffering are virtual paths on san devices over SDD driver. Use the datapath command to map the relation between vpaths and hdisks - that is "datapath query device"
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone have an idea what this means? hdisk10 is part of vg1. (vg1 has 11 hdisks)
I get this msg every morning @ 5:04 CST
This is the orignal message:
A PROBLEM WAS DETECTED ON Fri Aug 17 03:02:09 PDT 2001 801014
The Service Request Number(s)/Probable Cause or... (2 Replies)
Discussion started by: Optimus_P
2 Replies
2. AIX
Hi,
I have a question about AIX vpaths and the fbvols you create via dscli on a DS8100 storage. Is there any command or any way to look which fbvol corresponds which vpath on operating system like the command fget_config -Av on a FastT storage system? I tried the datapath query device, datapath... (1 Reply)
Discussion started by: samaks
1 Replies
3. Shell Programming and Scripting
Hi all,
I need to check the contents of my vpath directive in my file. Is it possible to check the contents of the vpath directive as we do for a variable like @echo '$vpath' .
Please let me know the above is correct or suggest me the correct one.
Thanks in advance.
-Jerry (6 Replies)
Discussion started by: jerryragland
6 Replies
4. AIX
Hi everyone,
how can I check if I have LUNs in a server and the LUNīs vpath in AiX?
thx (5 Replies)
Discussion started by: jcpetela
5 Replies
5. AIX
Hello everyone:
just want to know how to get the name of the shark in which the vpath is?
thanks (2 Replies)
Discussion started by: jcpetela
2 Replies
6. AIX
Hello all,
I need to run successfully this command :
1:root@abcd:/root # lscfg -vl vpathXY
lscfg: device vpathXY not found.
1:root@abcd:/root # echo $?
1
If I run it on another server I will get no output which is ok :
1:root@efgh:/root # lscfg -vl vpathAB
1:root@efgh:/root # echo... (0 Replies)
Discussion started by: phobus
0 Replies
7. AIX
Hello all,
I need to run successfully this command :
1:root@abcd:/root # lscfg -vl vpathXY
lscfg: device vpathXY not found.
1:root@abcd:/root # echo $?
1
If I run it on another server I will get no output which is ok :
1:root@efgh:/root # lscfg -vl vpathAB
1:root@efgh:/root # echo $?... (4 Replies)
Discussion started by: phobus
4 Replies
8. AIX
Hi all,
I'm getting some errors on AIX regarding Flashcopy and volume group hard disks.
The script that activates flashcopy showed this errors:
Recreating Flashcopy for lun01_A1
Performing syntax check...
Syntax check complete.
Executing script...
Script execution complete.
SMcli... (1 Reply)
Discussion started by: enux
1 Replies
9. Shell Programming and Scripting
Hi,
Planning to implement script to fetch whether the hdisks are in proper sequence. Need output for incorrect sequence
Correct
#lspv
hdisk0
hdisk1
hdisk2
::::::::::::
hdisk5
Incorrect sequence
#lspv
hdisk0
hdisk6
hdisk7
hdisk10
Any idea pls share (2 Replies)
Discussion started by: ksgnathan
2 Replies
10. AIX
Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
RAW(8) System Administration RAW(8)
NAME
raw - bind a Linux raw character device
SYNOPSIS
raw /dev/raw/raw<N> <major> <minor>
raw /dev/raw/raw<N> /dev/<blockdev>
raw -q /dev/raw/raw<N>
raw -qa
DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device
driver does not even have to be accessible (it may be loaded on demand as a kernel module later).
raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N>
is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either
in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file.
The bindings already in existence can be queried with the -q option, which is used either with a raw device filename to query that one
device, or with the -a option to query all bound raw devices.
Unbinding can be done by specifying major and minor 0.
Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw
device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache
entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver
can support DMA, then no data copying at all is required to complete the I/O.
Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor-
rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the
data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices.
OPTIONS
-q, --query
Set query mode. raw will query an existing binding instead of setting a new one.
-a, --all
With -q , specify that all bound raw devices should be queried.
-h, --help
Display help text and exit.
-V, --version
Display version information and exit.
BUGS
The Linux dd(1) command should be used without the bs= option, or the blocksize needs to be a multiple of the sector size of the device
(512 bytes usually), otherwise it will fail with "Invalid Argument" messages (EINVAL).
Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate,
but is regarded either a bug or a feature depending on who you ask!
NOTES
Rather than using raw devices applications should prefer open(2) devices, such as /dev/sda1, with the O_DIRECT flag.
AUTHOR
Stephen Tweedie (sct@redhat.com)
AVAILABILITY
The raw command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux August 1999 RAW(8)