I tried the same syntax as you did at first, having used it in the 2.4
days. But the world has changed.
Lately, this is how it works for me: (cut-n-pasted so this may be rough)
insmod /lib/modules/`uname -r`/kernel/drivers/s390/scsi/zfcp.ko
echo 1 > /sys/bus/ccw/drivers/zfcp/0.0.fcfc/online
echo 0x55550000abcd6789 > /sys/bus/ccw/drivers/zfcp/0.0.fcfc/port_add
echo 0x0001000000000000 >
/sys/bus/ccw/drivers/zfcp/0.0.fcfc/0x55550000abcd6789/unit_add
Kernel pseudo files for the LUN are then found under
/sys/bus/ccw/drivers/zfcp/0.0.fcfc/0x55550000abcd6789/0x0001000000000000,
where "fcfc" is the IO address of the FCP device ("device" to the Linux
system, but "channel" in the SAN context), 55550000abcd6789 is the WWPN
of the storage system, and 0001000000000000 is the LUN defined there.
(All of these numbers are made up. Fill in your own real WWPN, LUN, and
FCP addr.)
Magically, "sda" showed up under /proc/partitions and was immediately
useable. I threw an EXT2 filesystem on the volume (no partitioning).
Only just today, I got a second path to that LUN. It seems to work also.
That's a whole nutha story.
-- R,
Michael Harvey <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[email protected]>
08/08/2006 12:30 PM
Please respond to Linux on 390 Port <[email protected]>
From
Michael Harvey <[EMAIL PROTECTED]>
To
[email protected]
cc
Subject
Re: ECKD vs FBA problem on MF Linux Lpar
Another question on same issue, let me know if you can help.
When I try to 'MAP' the FBA disk using the 'ZFCP' module this is what
I get
:
LNOUC4D:~ # insmod zfcp map="0x0406 0x01:0x50060482ccb539c8
0x0:0x0107000000000000"
insmod: can't read 'zfcp': No such file or directory
LNOUC4D:~ #
Can see what I am missing !
Thank You.
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Troth
Sent: Monday, August 07, 2006 10:50 AM
To: [email protected]
Subject: Re: ECKD vs FBA problem on MF Linux Lpar
There may be a typo in 'mkinitrd' and its cousins, because it also
flags
your 101 as CKD. There is only the one driver: DASD, with varying
sub-components. Also, some commands will not work with an FBA disk,
notably 'dasdfmt' and 'fdasd'. While 'fdisk' does work, last time
I
used it there was some confusion in its logic when run against FBA.
Note
that FBA does not require the low-level format function of 'dasdfmt'.
It
is already blocked.
No shame in using /dev/dasdd as un-partitioned! If it is to be LVM
fodder, that makes all the more sense. But if you abso-blasto-lutely
must partition it, then CP LINK the EDEV to CMS and FORMAT it there.
You'll then automagically get "LDL" (zLinux disk layout) instead of
"CDL" (compatible disk layout, which requires CKD). CMS FORMAT will
skip the block creation on FBA disks and simply lay a CMS filesystem
onto
the disk. Linux will see that and do its own thing, resulting in LDL
with one (and only one) partition, /dev/dasdd1.
-- R,
Michael Harvey <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[email protected]>
08/07/2006 10:06 AM
Please respond to Linux on 390 Port <[email protected]>
From
Michael Harvey <[EMAIL PROTECTED]>
To
[email protected]
cc
Subject
ECKD vs FBA problem on MF Linux Lpar
We have the Linux Lpar under ZVm and connected thru a McData Switch. We
see
the following on device eg. 406 as FBA but later is seen as ECKD device.
What informational source can I use to do a step by step allocation of
FBA
devices or understnd more on this topic. Thank You.
EDEV 0406 TYPE FBA ATTRIBUTES SCSI
PATHS:
FCP_DEV: 4006 WWPN: 50060482CCB539C8 LUN: 0107000000000000
set edev 406 type fba attr scsi fcp_dev 4006 wwpn 50060482ccb539c8 lun
010700000
0000000
When we do a lsdasd, we can see the disk :
LNOUC4D:/dev/scsi # lsdasd
0.0.0100(ECKD) at ( 94: 0) is dasda : active at blocksize 4096,
546840 blocks, 2136 MB
0.0.0101(FBA ) at ( 94: 4) is dasdb : active at blocksize 512, 524288
blocks, 256 MB
0.0.0102(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 54000
blocks, 210 MB
0.0.0406(FBA ) at ( 94: 12) is dasdd : active at blocksize 512,
71454720 blocks, 34890 MB
I am able to go into yast and creat an LVM and Filesystem,
but when I do a mkinitrd it thinks the DASD is an ECKD device instead of
FBA, this is wrong ?
Root device: /dev/dasda1 (mounted on / as ext3)
Module list: jbd ext3 dasd_eckd_mod dasd_fba_mod
Kernel image: /boot/image-2.6.5-7.244-s390x
Initrd image: /boot/initrd-2.6.5-7.244-s390x
Shared libs: lib64/ld-2.3.3.so lib64/libblkid.so.1.0 lib64/libc.so.6
lib64/li
bselinux.so.1 lib64/libuuid.so.1.2
Modules: kernel/fs/jbd/jbd.ko kernel/fs/ext3/ext3.ko
kernel/drivers/s390/
block/dasd_mod.ko kernel/drivers/s390/block/dasd_eckd_mod.ko
kernel/drivers/s390
/block/dasd_fba_mod.ko
DASDs: 0.0.0100(ECKD) 0.0.0101(ECKD) 0.0.0102(ECKD) 0.0.0406
(ECKD)
Including: udev
initrd updated, zipl needs to update the IPL record before IPL!
----------------------------------------------------------------------
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 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 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 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
