Is this for a program or fstab entry which is expecting that disk to always
appear at /dev/dasdp?
Because if you can edit your source, it would be safer to refer to your
disks by path (such as /dev/disk/by-path/ccw-0.0.0154) rather than by their
dasd[a-z][a-z]* names. The path will always correspond to the underlying
virtual device number, while the by-letter names are dependent on the order
in which they happen to be brought online.
Also, if you need to find the associated dasd* name for a disk whose vdev
you know, you can use the following:
readlink -f /dev/disk/by-path/ccw-0.0.${vdev}
...like this:
myhostname:/etc/udev/rules.d # readlink -f /dev/disk/by-path/ccw-0.0.0100
/dev/dasda
On Thu, Sep 29, 2011 at 10:59 AM, Peter E. Abresch Jr. - at Pepco <
[email protected]> wrote:
> Under SLES10, we see the following:
>
> 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize 4096,
> 600840 blocks, 2347 MB
> 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096,
> 600840 blocks, 2347 MB
> 0.0.0152(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096,
> 600840 blocks, 2347 MB
> 0.0.0153(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096,
> 600840 blocks, 2347 MB
> 0.0.0154(ECKD) at ( 94: 16) is dasde : active at blocksize 4096,
> 600840 blocks, 2347 MB
> 0.0.015f(ECKD) at ( 94: 60) is dasdp : active at blocksize 4096,
> 150840 blocks, 589 MB
>
> Notice that 0.0.015f is dasdp
>
>
> Under SLES11, we see the following:
>
> Bus-ID Status Name Device Type BlkSz Size Blocks
>
> ==============================================================================
> 0.0.0150 active dasda 94:0 ECKD 4096 2347MB 600840
> 0.0.0151 active dasdb 94:4 ECKD 4096 2347MB 600840
> 0.0.0152 active dasdc 94:8 ECKD 4096 2347MB 600840
> 0.0.0155 active dasdd 94:12 ECKD 4096 2347MB 600840
> 0.0.0156 active dasde 94:16 ECKD 4096 2347MB 600840
> 0.0.015f active dasdf 94:20 ECKD 4096 589MB 150840
>
> Notice that 0.0.015f is dasdf rather than dasdp. How can I insure that
> 0.0.015f is always dasdp?
>
> I read that this behavior had change but naturally now that I need this
> doc, I cannot find it anywhere. I do not remember where I read it. Errrr.
>
> Can anyone point me in the right direction? Thanks as always.
>
> Peter
>
> This Email message and any attachment may contain information that is
> proprietary, legally privileged, confidential and/or subject to copyright
> belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
> intended solely for the use of the person(s) to which it is addressed. If
> you are not an intended recipient, or the employee or agent responsible for
> delivery of this Email to the intended recipient(s), you are hereby
> notified
> that any dissemination, distribution or copying of this Email is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and permanently delete this Email and any copies. PHI
> policies expressly prohibit employees from making defamatory or offensive
> statements and infringing any copyright or any other legal right by Email
> communication. PHI will not accept any liability in respect of such
> communications.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
