EDEV: Oh, I missed that "minor detail" ... . I think to recall that EMC at some point in time really allowed to configure their systems to present SCSI disks as channel attached FBA as you asked for. Therefore I was misled. Don't know whether this feature still exists, though. Perhaps Mike can shed some light on that ...
Best regards, Ingo -- Ingo Adlung, STSM, System z Linux and Virtualization Architecture mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 Linux on 390 Port <[email protected]> wrote on 08.08.2006 23:31:47: > Ah! I see what you meant. > Yes, he was using EDEV. Neat stuff, EDEV. VM talks to the SAN and > presents FBA to the guest. > Wouldn't it be ... "elegant" ... if the storage vendors presented FBA to > the System z host? > > -- R, > > > > > > Ingo Adlung <[EMAIL PROTECTED]> > > Sent by: Linux on 390 Port <[email protected]> > > > > > 08/08/2006 04:33 PM > Please respond to Linux on 390 Port <[email protected]> > > From > Ingo Adlung <[EMAIL PROTECTED]> > To > [email protected] > cc > > Subject > Re: ECKD vs FBA problem on MF Linux Lpar > > > > > > > > Wow ... such an interesting suggestion. You mean, Ingo, that EMC > might > > speak FBA on the IBM "channel"? > > Hi Rick, when you sneak through Mike's initial mail (snippet) > > > 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 ? > > it suggests for exactly this being the case - i.e. my brain can't be that > off :-) > > While I remember that we had heart about this feature some years ago I > don't > think we ever had an EMC box to test with ourselves. If we could nail down > the problem Mike describes it could certainly become a nice add-on feature > :-) > > Best regards, > Ingo > > -- > Ingo Adlung, > STSM, System z Linux and Virtualization Architecture > mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 > > Linux on 390 Port <[email protected]> wrote on 08.08.2006 19:29:00: > > > Wow ... such an interesting suggestion. You mean, Ingo, that EMC > might > > speak FBA on the IBM "channel"? > > > > I have tried, and tried, and tried to get the storage vendors and/or > > in-house storage management teams to present FBA (eg: 9336) on the > > channel. I get the "deer in the headlights" response every time. They > > just don't seem to know what disk is if it isn't CKD. Oh ... SAN, > maybe, > > but that's on a different wire. Plug the same system into an IBM > > processor and it must be CKD (3390, maybe 3380). > > > > It would be a great boon to all of us (VM, VSE, Linux) if EMC and STK > > and IBM would give us an FBA handle on SAN volumes. Think about it! SAN > > on one side, which can talk to z/VM and to zLinux, but also to > Solaris, > > AIX, Windows, but then also FBA to z/VM and to zLinux as FBA without > > EDEV overhead. (Don't get me wrong: EDEV is great, but it's a hack, > and > > it's heavy.) > > > > The CKD "wrapper" around the data which all DASD vendors now appear to > > mandate (if using an IBM strand of fibre) is overhead. The disk > system > > must wrap-up the data; Linux and CMS (even CP to some extent) must > then > > un-wrap it. Overhead on both ends. [sigh] Why is it that turning off > > this overhead is such a difficult concept to grasp? > > > > -- R, > > > > > > > > > > > > Ingo Adlung <[EMAIL PROTECTED]> > > > > Sent by: Linux on 390 Port <[email protected]> > > > > > > > > > > 08/08/2006 01:05 PM > > Please respond to Linux on 390 Port <[email protected]> > > > > From > > Ingo Adlung <[EMAIL PROTECTED]> > > To > > [email protected] > > cc > > > > Subject > > Re: ECKD vs FBA problem on MF Linux Lpar > > > > > > > > > > > > > > I'm confused. I think to recall that with EMC storage subsystems you > > could surface SCSI disks as FBA disks, hence the fba discipline of the > > dasd device driver would detect it and take care of it ... is this the > > use case described initially? > > > > In this case zfcp would be completely out of the picture ... > > > > Best regards, > > Ingo > > > > -- > > Ingo Adlung, > > STSM, System z Linux and Virtualization Architecture > > mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 > > > > Linux on 390 Port <[email protected]> wrote on 08.08.2006 > 18:57:51: > > > > > That looks like you don't have the zfcp kernel module on your system. > > > What does: > > > find /lib/modules/`uname -r` -iname "*zfcp*" > > > show you? > > > > > > > > > Mark Post > > > > > > -----Original Message----- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > > Michael Harvey > > > Sent: Tuesday, August 08, 2006 12:30 PM > > > To: [email protected] > > > 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. > > > > > > ---------------------------------------------------------------------- > > > 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 > > > ---------------------------------------------------------------------- > 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
