public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: kvm-devel@lists.sourceforge.net,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_blk: allow read-only disks
Date: Sat, 17 May 2008 14:01:56 +1000	[thread overview]
Message-ID: <200805171401.59076.rusty@rustcorp.com.au> (raw)
In-Reply-To: <482D53BB.2030203@wpkg.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/

  reply	other threads:[~2008-05-17  4:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  9:17 [PATCH] virtio_blk: allow read-only disks Christian Borntraeger
2008-05-16  9:28 ` Tomasz Chmielewski
2008-05-17  4:01   ` Rusty Russell [this message]
2008-05-16 14:25 ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200805171401.59076.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=mangoo@wpkg.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox