All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard Bloch <edi@gmx.de>
To: dm-devel@redhat.com
Subject: Re: Strange data corruption with RW snapshots
Date: Thu, 6 Oct 2005 18:59:24 +0200	[thread overview]
Message-ID: <20051006165924.GA22504@debian> (raw)
In-Reply-To: <20051005161610.GA5696@debian>

#include <hallo.h>
* Eduard Bloch [Wed, Oct 05 2005, 06:16:10PM]:
> #include <hallo.h>
> * Kevin Corry [Wed, Oct 05 2005, 10:49:30AM]:

> So I must assume there is something wrong with the cloop driver, and
> dm-snapshot is the only way to reproduce that. The symptoms look similar
> to non-reentrant programs, but I didn't try to inspect the exact
> behaviour of dm-snapshot when reading from cloop device yet.

The problem was in the cloop driver, it has also been found and fixed by
the Ubuntu guys without telling anyone else. The new packages of cloop
will solve the problem. Sorry for the noise.

Eduard.
-- 
Wer viel spricht hat weniger Zeit zum Denken.
		-- Indisches Sprichwort

      reply	other threads:[~2005-10-06 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 11:20 Strange data corruption with RW snapshots Eduard Bloch
2005-10-05 15:49 ` Kevin Corry
2005-10-05 16:16   ` Eduard Bloch
2005-10-06 16:59     ` Eduard Bloch [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=20051006165924.GA22504@debian \
    --to=edi@gmx.de \
    --cc=dm-devel@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.