Not quite what I meant. I was thinking of situations where the original system would be temporarily shut down during the cloning or backup operation. In this case, the "owner" would access the file system read-write, but it'd be safer for the "cloner" to only have read-only access to those disks. They would not, however, be accessing these file systems at the same time.
On Wed, Aug 25, 2010 at 12:34 PM, Edmund R. MacKenty < [email protected]> wrote: > On Wednesday, August 25, 2010 12:21:50 pm Mark Post wrote: > > This would be a very dangerous practice, and one I always tell people to > > never use. If a file system is going to be shared between Linux systems, > > it needs to be mounted read-only by all systems, including the "owner" of > > it. > > Thanks Mark! I was writing a similar reply when yours arrived. Having a > read-write mount to a shared Linux filesystem is just asking for it to be > corrupted, because of multiple caches being unaware of each other. > Please do not do that! > - MacK. > ----- > Edmund R. MacKenty > Software Architect > Rocket Software > 275 Grove Street - Newton, MA 02466-2272 - USA > Tel: +1.617.614.4321 > Email: [email protected] > Web: www.rocketsoftware.com > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
