From: Malahal Naineni <malahal@us.ibm.com>
To: dm-devel@redhat.com
Subject: Re: How to test the read/write flow of dm-target.
Date: Fri, 28 Jan 2011 11:42:41 -0800 [thread overview]
Message-ID: <20110128194241.GB4616@us.ibm.com> (raw)
In-Reply-To: <AANLkTimQjYdRqLFpuystxuN5hM=rGirj9XBiA_zDkG7+@mail.gmail.com>
nishant mungse [nishantmungse@gmail.com] wrote:
> Hi,
>
> I've created a device mapper target and I wanna test its read and
> write mechanisms. I created a device using this target and tried to
> write a filesystem on to the device.
>
> My target is creating roughly two outgoing bios per incoming bio.
> Which is maybe why I'm not able to get a proper log after running the
> mke2fs command as while writing the filesystem, there are massive
> amounts of writes performed on the device.
>
> So, I tried to use the cat command to directly write to the device
> file. The write is being performed for sure because I'm able to view
> the data written to the underlying device.
>
> But there is no output when I try to read the device file contents using cat.
>
> Is there any other way to test the read/write workflows of a dm target
> that can give out a proper log ?
I am not sure what you mean by 'proper log'. I would use 'dd' with
direct I/O to avoid cache so that every read and write directly go to the
device. I don't think you can do that with 'cat' command.
next prev parent reply other threads:[~2011-01-28 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 5:06 How to test the read/write flow of dm-target nishant mungse
2011-01-28 19:42 ` Malahal Naineni [this message]
2011-01-30 18:37 ` nishant mungse
2011-01-30 19:27 ` Milan Broz
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=20110128194241.GB4616@us.ibm.com \
--to=malahal@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox