2006/10/29, Vic Cross <[EMAIL PROTECTED]>:
Lee Stewart wrote: > Depends on when you want to check it... > > After it's activated, look at /proc/dasd/devices > 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize: > 4096, 600840 blocks, 2347 MB > 0.0.0190(ECKD) at ( 94: 24) is dasdg (ro): active at blocksize: > 4096, 19260 blocks, 75 MB > > Note 190 (/dev/dasdg) above is flagged (ro) since it's a read only > device. (This is SLES9). In that case it's (ro) because the dasd driver has been told to activate it so. If the DASD driver has not been told RO, it will happily activate it as RW and then fail dismally with any attempted writes (the kernel errors Eric mentioned). I think what Eric requires is a way to determine if VM has given it to Linux RO, in order for Linux to activate it the right way... The hcp/vmcp methods mentioned will be the way to do this. Cheerio, Vic Cross
Exactly! Thanks everybody for your help! -- Eric Gaulin ---------------------------------------------------------------------- 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
