All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: dm-thin: commit metadata bug
Date: Fri, 5 Aug 2011 14:13:39 +0100	[thread overview]
Message-ID: <20110805131338.GA1882@ubuntu> (raw)
In-Reply-To: <Pine.LNX.4.64.1108050856100.19545@hs20-bc2-1.build.redhat.com>

On Fri, Aug 05, 2011 at 08:59:09AM -0400, Mikulas Patocka wrote:
> There is a bug in committing metadata --- you can't commit metadata if 
> there is any copying or zeroing in flight. The problem is that in this 
> case, the block you are copying to is already allocated, but it is not 
> linked anywhere in the metadata. So it creates lost blocks in case of 
> crash.

Yes, well known and documented.  We take this hit, fsck will repair.

- Joe

      reply	other threads:[~2011-08-05 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 12:59 dm-thin: commit metadata bug Mikulas Patocka
2011-08-05 13:13 ` Joe Thornber [this message]

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=20110805131338.GA1882@ubuntu \
    --to=thornber@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.