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
