>Anyone know how to tell what this error is? Even when mounting a filesystem ro, the filesystem tries to update some things in case the block device is read+write (tried this with ext2&3). We do not detect if a device is read-only, because we did not find a nice way to do so (our best idea was read a block and write it again to see if you get a command reject indication back, another one was to parse the "#cp q dasd" output). You can specify if a device is read-only at run-time using "blockdev --setro /dev/dasda" or "blockdev --setrw /dev/dasda". In your parmfile or when using /proc/dasd/devices to add devices you can use (ro) after the device number to preset the device to be read-only. If anyone knows a good method to autodetect if a device is read-only or not, please let us know!
with kind regards Carsten Otte -- I saw screens of green, red messages too, then came blue, shubidu And i think to myself, what a wonderful world ---------------------------------------------------------------------- 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
