1. chccwdev -e 0190 ----> online dasd 2. lsdasd 0190 ---> you see dasdx 3. cmsfsvol -d /dev/dasdx ---> ok
sva Linux on 390 Port <[email protected]> написано 05.04.2007 17:26:47: > In what you listed, "VMC52R" is the CP label on the whole disk of which > your 190 is but a slice. It's way outside the scope of what CMSFS can do. > > Linux presents the disks just like any Unix or POSIX system would: /dev/ > something > You'll have to figure out where the 190 (or 191 or whatever) is assigned. > Look at /proc/dasd/devices. > > -- R; > > > > > > Mark Perry <[EMAIL PROTECTED]> > > Sent by: Linux on 390 Port <[email protected]> > > > > > 04/05/2007 08:57 AM > Please respond to Linux on 390 Port <[email protected]> > > From > Mark Perry <[EMAIL PROTECTED]> > To > [email protected] > cc > > Subject > Re: cmsfs and cmsfs.o > > > > > > > Richard Troth wrote: > >> Hi List and Rick. > >> SLES10 GA supplies an rpm for cmsfs (on CD2), but it does not include > >> cmsfs.o. > >> So basically the cms commands in the package can't be used, right? > >> > > > > The commands should all work fine. > > > > You're confusing the CMSFS utility from the CMSFS driver. They are > > independent. The driver lets you mount CMS disks. The utility lets you > > read them, or read files from them, without mounting them. > > > > The commands should be statically linked against their common library. > > That would be "cmsfs.a". It's "cmsfs.o" you said is missing, not " > > cmsfs.a" nor "cmsfs.so". If the commands were linked against the > shared > > library, it would be the ".so" form. More likely, they were linked > > against the static library, which is the ".a" form which would have > > been deleted before the RPM was generated. > > > > Historically, kernel modules were named ".o". More recently they are > > named ".ko" because the other extension has meaning apart from kernel > > space. There should be no "cmsfs.o" at all if you are running an > > up-to-date Linux. You might find "cmsfs.ko" (not likely since it is > > broken) or possibly "cmsfs.so" (not likely unless the distributor got > > waaaay too deep into the code), but no "cmsfs.o". > > > > I hope this helps. > > > > -- R; > > > > > Hi R, > OK makes sense, but i can't get cmsfsvol to work, maybe my lack of VM > expertise ;-) > > example: > > ihlscov0:~ # vmcp q v dasd > DASD 0190 3390 VMC52R R/O 107 CYL ON DASD 7841 SUBCHANNEL = 001A > DASD 0191 3390 VMC52U R/W 10 CYL ON DASD 7845 SUBCHANNEL = 0004 > DASD 019D 3390 VMC52R R/O 146 CYL ON DASD 7841 SUBCHANNEL = 001B > DASD 019E 3390 VMC52R R/O 250 CYL ON DASD 7841 SUBCHANNEL = 001C > DASD 0592 3390 VMC52R R/O 67 CYL ON DASD 7841 SUBCHANNEL = 001D > DASD 1000 3390 LX7846 R/W 10017 CYL ON DASD 7846 SUBCHANNEL = 0000 > DASD 1001 3390 LX782B R/W 10017 CYL ON DASD 782B SUBCHANNEL = 0001 > DASD 1002 3390 LX782C R/W 10017 CYL ON DASD 782C SUBCHANNEL = 0002 > DASD 1003 3390 LX782D R/W 10017 CYL ON DASD 782D SUBCHANNEL = 0003 > DASD 1100 9336 (VDSK) R/W 524288 BLK ON DASD VDSK SUBCHANNEL = 0005 > ihlscov0:~ # cmsfsvol VMC52R > LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL > open(): No such file or directory > cannot open 'VMC52R' > 'VMC52R' is not a CMS volume. > ihlscov0:~ # > > Any ideas? > > FYI I did the same with 190 and 191 with the same results. > > Mark > > ---------------------------------------------------------------------- > 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
