From: Bart Van Assche <bvanassche@acm.org>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Philip Shilane <philip.shilane@emc.com>,
Sonam Mandal <sonam.dp42@gmail.com>,
Erez Zadok <ezk@fsl.cs.sunysb.edu>
Subject: Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
Date: Tue, 29 Apr 2014 08:23:39 +0200 [thread overview]
Message-ID: <535F456B.5090600@acm.org> (raw)
In-Reply-To: <535ed0d2.0729e00a.4489.0c48@mx.google.com>
On 04/29/14 00:03, Vasily Tarasov wrote:
> See the documentation patch for more details.
Regarding that documentation: shouldn't the on-disk data structures be
documented ? Shouldn't it be documented how dm-dedup recovers from a
power failure ? Since different storage devices are used for data and
meta-data recovery from a power failure is nontrivial. How is it e.g.
guaranteed if a data block has been made persistent (e.g. via REQ_FUA)
and the refcount is increased for that data block that neither the data
nor the metadata for that data block is lost if a power failure occurs ?
Bart.
next prev parent reply other threads:[~2014-04-29 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 22:03 [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target Vasily Tarasov
2014-04-29 6:23 ` Bart Van Assche [this message]
2014-04-29 13:26 ` Vasily Tarasov
2014-05-05 18:24 ` Mike Snitzer
2014-05-06 13:43 ` Vasily Tarasov
2014-05-06 14:23 ` Mike Snitzer
2014-07-18 2:43 ` Mike Snitzer
2014-07-18 11:59 ` Vasily Tarasov
2014-07-18 13:29 ` Joe Thornber
2014-07-18 14:44 ` Mike Snitzer
2015-03-06 18:37 ` Vivek Goyal
2015-03-06 23:31 ` Akira Hayakawa
2015-03-07 21:31 ` Vasily Tarasov
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=535F456B.5090600@acm.org \
--to=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=philip.shilane@emc.com \
--cc=sonam.dp42@gmail.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.