From: Edward Thornber <thornber@redhat.com>
To: Dennis Yang <dennisyang@qnap.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Possible data corruption with dm-thin
Date: Fri, 1 Jul 2016 09:18:56 -0400 [thread overview]
Message-ID: <20160701131856.GB32440@roamer.bos.redhat.com> (raw)
In-Reply-To: <CAAR726KCTJnbJhU-XhAn0xv3RVEHZY-NFjSNnWqnuVVO6kR4xQ@mail.gmail.com>
Hi Dennis,
Sorry to take so long about getting back to you. There was a bug in
the btree library that I mistakenly thought was caused by my fix for
your problem. Anyway, could you try and recreate your problem with
these two patches applied please (patches are against v4.7-rc5 + my
usual thin-dev extras):
https://github.com/jthornber/linux-2.6/commit/ebdd99fc12acd0e9178831549896633171d5af1d
https://github.com/jthornber/linux-2.6/commit/c05989b59d091270c2bf7dd05bdb7a3575223529
Thanks,
- Joe
next prev parent reply other threads:[~2016-07-01 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 7:56 Possible data corruption with dm-thin Dennis Yang
2016-06-21 8:59 ` Zdenek Kabelac
2016-06-21 10:40 ` Dennis Yang
2016-06-21 10:46 ` Zdenek Kabelac
2016-06-24 13:55 ` Edward Thornber
2016-06-27 9:32 ` Dennis Yang
2016-07-01 13:18 ` Edward Thornber [this message]
2016-09-06 4:51 ` Dennis Yang
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=20160701131856.GB32440@roamer.bos.redhat.com \
--to=thornber@redhat.com \
--cc=dennisyang@qnap.com \
--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.