I have never understood why the driver does not automatically set the R/O flag when a write operation is rejected.
-- R; <>< 2009/6/15 Carsten Otte <[email protected]>: > Am Sun, 14 Jun 2009 01:34:35 +0200 > schrieb Rob van der Heij <[email protected]>: >> One of the problems is that S/390 has no way to sense the R/O setting >> of the disk, so we can't pass that to the mount (like you have with a >> CD for example). The only way to tell is by trying to write to the >> disk.We did not think that was very elegant. >> >> But you can also tell the Linux dasd driver to not write it, that >> should be more powerful than mount ro. It's probably through the >> hwcfg-* files. I believe that with that setting the mount will default >> to "ro" ? > You recall correctly. The parameter can also be set via the (ro) > suffix on dasd parameter line either as parameter to insmod when > loading dasd, or via kernel parameter (zipl). Like this: > dasd=1000,1001(ro),2000-20ff(ro) > ^^ dasd 1000 will be writable, 1001 and 2000-20ff are read only. > > All mounts of subject dasds will be read-only by default. The > parameter can be changed using the blockdev command (--setro option)*. > > * make sure you're not setting a disk to read-only that is currently > mounted read+write > > ---------------------------------------------------------------------- > 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
