From: Mike Snitzer <snitzer@redhat.com>
To: Erez Zadok <ezk@fsl.cs.sunysb.edu>
Cc: Vasily Tarasov <tarasov@vasily.name>,
Joe Thornber <thornber@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
device-mapper development <dm-devel@redhat.com>,
Shilane Philip <philip.shilane@emc.com>,
Sonam Mandal <sonam.dp42@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
Date: Wed, 26 Nov 2014 11:47:18 -0500 [thread overview]
Message-ID: <20141126164717.GA30610@redhat.com> (raw)
In-Reply-To: <A29EA256-362D-43EC-ABF5-FB10644E6DF1@fsl.cs.sunysb.edu>
On Wed, Nov 26 2014 at 11:36am -0500,
Erez Zadok <ezk@fsl.cs.sunysb.edu> wrote:
> Mike, Vivek,
>
> Thank you for the effort and especially for adding more man-power to
> this review. We know how busy you guys are so it’s understandable
> that things can take a while to get started. Either way, I’ve
> instructed my students to give this project the highest priority,
> especially once we receive comments from you.
Great. So along those lines have you guys worked on userspace tools
that can verify/repair the ondisk metadata?
That will be a prereq for upstream inclusion (at least for dm-dedup to
become anything but "experimental").
dm-cache and dm-thin targets have these types of tools
(thin_{check,repair}, cache_{check,repair}, etc). Upstream repo is here
(misnamed, gets packaged into device-mapper-persistent-data rpm on
Fedora, RHEL, CentOS, etc):
https://github.com/jthornber/thin-provisioning-tools
Mike
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2014-11-26 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:56 [PATCH RFCv2 01/10] dm-dedup: main data structures Vasily Tarasov
2014-09-26 15:24 ` Mike Snitzer
2014-09-29 13:34 ` Vasily Tarasov
2014-10-17 17:11 ` Vasily Tarasov
2014-10-17 17:42 ` Mike Snitzer
2014-11-26 15:38 ` Mike Snitzer
2014-11-26 16:36 ` Erez Zadok
2014-11-26 16:47 ` Mike Snitzer [this message]
2014-11-26 18:35 ` Vasily Tarasov
2014-12-04 1:21 ` Darrick J. Wong
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=20141126164717.GA30610@redhat.com \
--to=snitzer@redhat.com \
--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 \
--cc=tarasov@vasily.name \
--cc=thornber@redhat.com \
--cc=vgoyal@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.