dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: device-mapper development <dm-devel@redhat.com>,
	Ondrej Kozina <okozina@redhat.com>
Cc: Mike Snitzer <msnitzer@redhat.com>
Subject: Re: [PATCH 8/9] dm crypt: offload writes to thread
Date: Tue, 01 Apr 2014 21:08:56 +0200	[thread overview]
Message-ID: <533B0EC8.3090004@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1404011355500.12362@file01.intranet.prod.int.rdu2.redhat.com>

On 04/01/2014 08:01 PM, Mikulas Patocka wrote:
>> 1) mdadm -C -l 5 -n 3 -c 64 --assume-clean /dev/md0 /dev/sd[xyz]
>> 2) run 2/dmcrypt-all-verify.sh
> 
> I tried to run "./dmcrypt-all-verify.sh --dev /dev/md0 --testdir 
> /mnt/test" and the result was this.
> 
> That script is somehow buggy because it attempts to copy files that I have 
> in /usr/src to the test filesystem. It fills up the test filesystem and 
> fails. I don't know why is it trying to copy files not related to the test.

Hi Mikulas,

if it is the test I wrote years ago, it was in principle a hack,
I need some filesystem with a lot files of different sizes.

So I simply packed /usr and checked hash of all files before
and after unpacking to test dmcrypt device.

IMHO there should be some prepared archive which is just unpacked,
not that it uses live /usr.
(Obviously it need large enough device :-)

But anyway, despite it is quite stupid test, it already proved
to be very useful (I remember it discovered bugs in various patches
several times).

A IIRC it used several fs types and several encryption types
(including null encryption which removes crypto layer influence,
testing pure dmcrypt bio handling).

Milan

  reply	other threads:[~2014-04-01 19:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 20:11 [PATCH 0/9] dm crypt: improve cpu scalability Mike Snitzer
2014-03-28 20:11 ` [PATCH 1/9] dm crypt: fix cpu hotplug crash by removing per-cpu structure Mike Snitzer
2014-03-28 20:11 ` [PATCH 2/9] block: use kmalloc alignment for bio slab Mike Snitzer
2014-03-28 20:11 ` [PATCH 3/9] dm crypt: use per-bio data Mike Snitzer
2014-03-28 20:11 ` [PATCH 4/9] dm crypt: use unbound workqueue for request processing Mike Snitzer
2014-03-28 20:11 ` [PATCH 5/9] dm crypt: don't allocate pages for a partial request Mike Snitzer
2014-03-28 20:11 ` [PATCH 6/9] dm crypt: avoid deadlock in mempools Mike Snitzer
2014-03-28 20:11 ` [PATCH 7/9] dm crypt: remove io_pool Mike Snitzer
2014-03-28 20:11 ` [PATCH 8/9] dm crypt: offload writes to thread Mike Snitzer
2014-04-01 16:27   ` Ondrej Kozina
2014-04-01 16:32     ` Mike Snitzer
2014-04-01 18:15       ` Mikulas Patocka
2014-04-01 18:23         ` Mike Snitzer
2014-04-02  6:55         ` Ondrej Kozina
2014-04-01 18:01     ` Mikulas Patocka
2014-04-01 19:08       ` Milan Broz [this message]
2014-03-28 20:11 ` [PATCH 9/9] dm crypt: sort writes Mike Snitzer
2014-03-29  8:11   ` Milan Broz
2014-03-31 12:39     ` Mike Snitzer
2014-03-31 23:37       ` Akira Hayakawa
2014-04-01  1:01         ` Mike Snitzer
2014-04-01 17:35           ` Milan Broz
2014-04-01 20:15             ` Alasdair G Kergon
2014-04-01 23:21           ` Akira Hayakawa
2014-04-02  3:19             ` Akira Hayakawa
2014-04-02  3:38               ` Mike Snitzer
2014-04-02  4:18                 ` Akira Hayakawa

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=533B0EC8.3090004@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=msnitzer@redhat.com \
    --cc=okozina@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).