From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH] virtio_blk: allow read-only disks Date: Sat, 17 May 2008 14:01:56 +1000 Message-ID: <200805171401.59076.rusty@rustcorp.com.au> References: <200805161117.03439.borntraeger@de.ibm.com> <482D53BB.2030203@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Christian Borntraeger , virtualization@lists.linux-foundation.org To: Tomasz Chmielewski Return-path: In-Reply-To: <482D53BB.2030203@wpkg.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org On Friday 16 May 2008 19:28:27 Tomasz Chmielewski wrote: > Christian Borntraeger schrieb: > > Hello Rusty, > > > > sometimes it is useful to share a disk (e.g. usr). To avoid file system > > corruption, the disk should be mounted read-only in that case. > > Although it is done at a different level here, I wanted to note that > mounting a filesystem read-only does not necessarily mean the system will > not try to write to it. This is the case for ext3, for example - when > mounted ro, system will still reply the journal and do some writes etc. > > The patch, however, should take care of that, too, as it is completely > different place it is made ro. Note I'm assuming that the host will deny writes. Telling the guest is merely politeness. Cheers, Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/