qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: benoit.canet@irqsave.net, jcody@redhat.com,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [RFC] qcow2 journalling draft
Date: Fri, 6 Sep 2013 11:57:03 +0200	[thread overview]
Message-ID: <20130906095703.GG2588@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20130906092053.GA22552@T430s.nay.redhat.com>

Am 06.09.2013 um 11:20 hat Fam Zheng geschrieben:
> On Wed, 09/04 11:39, Kevin Wolf wrote:
> > First of all, excuse any inconsistencies in the following mail. I wrote
> > it from top to bottom, and there was some thought process involved in
> > almost every paragraph...
> > 
> > Am 04.09.2013 um 10:03 hat Stefan Hajnoczi geschrieben:
> > > On Tue, Sep 03, 2013 at 03:45:52PM +0200, Kevin Wolf wrote:
> > > > @@ -103,7 +107,11 @@ in the description of a field.
> > > >                      write to an image with unknown auto-clear features if it
> > > >                      clears the respective bits from this field first.
> > > >  
> > > > -                    Bits 0-63:  Reserved (set to 0)
> > > > +                    Bit 0:      Journal valid bit. This bit indicates that the
> > > > +                                image contains a valid main journal starting at
> > > > +                                journal_offset.
> > > 
> > > Whether the journal is used can be determined from the journal_offset
> > > value (header length must be large enough and journal offset must be
> > > valid).
> > > 
> > > Why do we need this autoclear bit?
> > 
> > Hm, I introduced this one first and the journal dirty incompatible bit
> > later, perhaps it's unnecessary now. Let's check...
> > 
> > The obvious thing we need to protect against is applying stale journal
> > data to an image that has been changed by an older version. As long as
> > the journal is clean, this can't happen, and the journal dirty bit will
> > ensure that the old version can only open the image if it is clean.
> > 
> > However, what if we run 'qemu-img check -r leaks' with an old qemu-img
> > version? It will reclaim the clusters used by the journal, and if we
> > continue using the journal we'll corrupt whatever new data is there
> > now.
> > 
> Why can old version qemu-img open the image with dirty journal in the first
> place? It's incompatible bit.

This is about a clean journal.

Kevin

  reply	other threads:[~2013-09-06  9:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 13:45 [Qemu-devel] [RFC] qcow2 journalling draft Kevin Wolf
2013-09-03 14:43 ` Benoît Canet
2013-09-04  8:03 ` Stefan Hajnoczi
2013-09-04  9:37   ` Benoît Canet
2013-09-04  9:39   ` Kevin Wolf
2013-09-04  9:55     ` Benoît Canet
2013-09-05  9:24       ` Stefan Hajnoczi
2013-09-05 15:26         ` Benoît Canet
2013-09-06  7:27           ` Kevin Wolf
2013-09-15 18:23             ` Benoît Canet
2013-09-05  9:21     ` Stefan Hajnoczi
2013-09-05 11:18       ` Kevin Wolf
2013-09-05 14:55         ` Stefan Hajnoczi
2013-09-05 15:20           ` Kevin Wolf
2013-09-05 15:56             ` Eric Blake
2013-09-06  9:20     ` Fam Zheng
2013-09-06  9:57       ` Kevin Wolf [this message]
2013-09-06 10:02         ` Fam Zheng
2013-09-04  8:32 ` Max Reitz
2013-09-04 10:12   ` Kevin Wolf
2013-09-05  9:35 ` Stefan Hajnoczi
2013-09-05 11:50   ` Kevin Wolf
2013-09-05 12:08     ` Benoît Canet
2013-09-06  9:59 ` Fam Zheng

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=20130906095703.GG2588@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).