Michael,
I don't disagree with what you're saying. Had to teach that to the WAS folk the
hard way.
For the sake of discussion what I was asking is different that the crux of this
thread.
We have a WebSphere maintenance system. It has two VM disk devices 206 and 216.
It has them defined R/W, but mounted. They are ext2 disks. At any one
time ONE of the devices is the active WebSphere root disk. The other is the one
to which maintenance is applied.
The WebSphere guests also have these disks defined to them by CP link commands
in the profile exec at startup. For consistency, they are also 206/216.
These WebSphere disks are linked R/O. At any one time ONLY the 'active master'
disk is mounted to a guest but they are both defined to the guest so
they can be switched out to test maintenance. We never write to the active
Master disk.
So, even though the VM image sees the disk as RO via the CP link, when Linux
comes up, it does NOT see these as RO by default, even though FSTAB has
the active disk mounted RO. the contents of /proc/dasd/devices never shows the
RO linked disks as being R/O even though they are from a VM
perspective.
So the question I am asking is WHY?
Michael MacIsaac <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
<[email protected]>
To
[email protected]
cc
06/08/2006 07:12 AM
Subject
Re:
Mounting ext3 disk read-only as ext2
Please respond to
Linux on 390 Port <[email protected]>
James,
> How do you tell Linux what VM already knows (The disk is RO) during
startup
> so you camt mount the VM specified RO mini-disk as RW to linux?
Good question. But it goes back to the basic premise that Mark pointed
out. I'll try to summarize
1) when you need to write to a disk that others have R/O, all others
should unmount the disk,
2) then the master can mount it, write to it and unmount it.
3) then all others can mount it R/O again.
This is a good, maybe even best, practice.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
----------------------------------------------------------------------
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
