From: Akira Hayakawa <ruby.wktk@gmail.com>
To: device-mapper development <dm-devel@redhat.com>,
Vasily Tarasov <tarasov@vasily.name>
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: Sat, 07 Mar 2015 08:31:28 +0900 [thread overview]
Message-ID: <54FA38D0.8090002@gmail.com> (raw)
In-Reply-To: <20150306183722.GD15736@redhat.com>
Vasily,
I recommend you to add tests into dmts
https://github.com/jthornber/device-mapper-test-suite
This testing framework can eliminate such trivial bugs.
And the tests become available to other developers are
valuable too.
It's written in Ruby and Joe designed carefully. So it's
really easy to add tests.
- Akira
On 2015/03/07 3:37, Vivek Goyal wrote:
> On Mon, Apr 28, 2014 at 06:03:06PM -0400, Vasily Tarasov wrote:
>> This is a request for comments for Dmdedup.
>
> mkfs.xfs crash the dm-dedup driver. mkfs.ext4 worked find though for me.
>
> Thanks
> Vivek
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
next prev parent reply other threads:[~2015-03-06 23:31 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
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 [this message]
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=54FA38D0.8090002@gmail.com \
--to=ruby.wktk@gmail.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 \
/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.