The only way I know how is to use a DB command: q system 3066
DASD 3066 ATTACHED SYSTEM 0001 L13066 LINUX20 0161 R/W Ready; T=0.01/0.01 14:18:34 q system 363a DASD 363A ATTACHED CPVOL 0109 511RES EREP 0191 R/W , OPERSYMP 0191 R/W , DISKACNT 0191 R/W MAINT 05E6 R/W , MAINT 05E5 R/W , MAINT 049E R/W MAINT 0500 R/W , MAINT 051D R/W , MAINT 049B R/W MAINT 0490 R/W , MAINT 0400 R/W , MAINT 0319 R/W MAINT 02CC R/W , MAINT 3200 R/W , MAINT 363A R/O MAINT 0123 R/O , MAINT 0201 R/W , EREP 0201 R/O VMUTIL 0191 R/W , VMSERVU 0191 R/W , LGLOPR 0191 R/W CMSBATCH 0195 R/W , SYSMON 0191 R/W , AUDITOR 0191 R/W MAINT 0191 R/W , THDBUSCH 0291 R/O , FTPSERVE 0191 R/W TCPIP 0191 R/W , TCPIP 0591 R/O , VSWCTRL1 0591 R/O The address on the command is a real address, not a virtual one. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 10/25/2006 1:59 PM >>> Hi, On z/VM side i have a DASD volume linked read only. But on linux side i need to find a way for detecting if that DASD device is in a read only state. with the following mount command: mount /mnt/data -o remount,rw I don't get any errors from de the mount command, and if i check the status of the mounted device with 'mount' alone, the filesystem looks like being mounted rw Of course i get a lots kernel errors! I have to build some scripts and it will be useful for me to validate this read-only state within my scripts. Any suggestions ? Thanks in advance! -- 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 ---------------------------------------------------------------------- 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
