From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] tool to account the written number of bytes to a block device
Date: Mon, 23 Aug 2010 09:14:50 +0200 [thread overview]
Message-ID: <4C721FEA.4020705@redhat.com> (raw)
In-Reply-To: <1282514263.3227.28.camel@fermat.scientia.net>
On 08/22/2010 11:57 PM, Christoph Anton Mitterer wrote:
> On Sun, 2010-08-22 at 18:01 +0200, Arno Wagner wrote:
>> I think /proc/diskstats is the place to look.
> Yeah,... of course,... I just didn't want to make my hands dirty with
> "programming" ;) (actually I didn't want to invent the cycle twice ;) )
iostat -N ?
(and save results after reboot)
Milan
next prev parent reply other threads:[~2010-08-23 7:14 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 14:57 [dm-crypt] Efficacy of xts over 1TB David Santamaría Rogado
2010-07-25 10:34 ` Arno Wagner
2010-07-25 11:18 ` Christoph Anton Mitterer
2010-07-25 12:29 ` Heinz Diehl
2010-07-25 12:25 ` Milan Broz
2010-07-25 13:14 ` Christoph Anton Mitterer
2010-07-25 13:52 ` Milan Broz
2010-07-25 22:37 ` Christoph Anton Mitterer
2010-07-26 0:14 ` Milan Broz
2010-07-26 20:38 ` Christoph Anton Mitterer
2010-07-27 8:46 ` [dm-crypt] Using plain64/plain IV (initialisation vector) in dm-crypt Milan Broz
2010-07-27 10:47 ` Arno Wagner
2010-07-27 14:17 ` Christoph Anton Mitterer
2010-07-27 16:08 ` Arno Wagner
2010-07-27 14:15 ` Christoph Anton Mitterer
2010-07-27 15:45 ` Mario 'BitKoenig' Holbe
2010-07-27 15:55 ` Milan Broz
2010-07-27 18:59 ` Christoph Anton Mitterer
2010-07-27 19:37 ` Arno Wagner
2010-07-27 18:58 ` Christoph Anton Mitterer
2010-07-27 19:35 ` Mario 'BitKoenig' Holbe
2010-07-28 8:42 ` Milan Broz
2010-08-20 21:11 ` [dm-crypt] XTS cipher mode limitations Christoph Anton Mitterer
2010-08-21 0:22 ` Arno Wagner
2010-08-22 12:50 ` [dm-crypt] XTS cipher mode limitations (FAQ additions) Christoph Anton Mitterer
2010-08-23 0:46 ` Arno Wagner
2010-08-25 9:36 ` Christoph Anton Mitterer
2010-08-22 12:56 ` [dm-crypt] tool to account the written number of bytes to a block device (was: XTS cipher mode limitations) Christoph Anton Mitterer
2010-08-22 16:01 ` Arno Wagner
2010-08-22 21:57 ` Christoph Anton Mitterer
2010-08-23 7:14 ` Milan Broz [this message]
2010-08-25 9:27 ` [dm-crypt] tool to account the written number of bytes to a block device Christoph Anton Mitterer
2010-08-24 16:19 ` [dm-crypt] XTS cipher mode limitations Ramius
2010-07-26 8:53 ` [dm-crypt] Efficacy of xts over 1TB Arno Wagner
2010-07-26 20:47 ` Christoph Anton Mitterer
2010-07-26 21:01 ` Arno Wagner
2010-07-26 21:28 ` Christoph Anton Mitterer
2010-07-26 21:35 ` Arno Wagner
2010-07-25 22:52 ` Christoph Anton Mitterer
2010-07-26 9:42 ` Mario 'BitKoenig' Holbe
2010-07-26 18:09 ` Arno Wagner
2010-07-27 18:16 ` [dm-crypt] Including the FAQ in the tarball? Christoph Anton Mitterer
2010-07-27 18:23 ` Arno Wagner
2010-07-29 8:17 ` Heinz Diehl
2010-07-25 15:32 ` [dm-crypt] Efficacy of xts over 1TB Arno Wagner
2010-07-25 22:48 ` Christoph Anton Mitterer
2010-07-25 23:42 ` Milan Broz
2010-07-26 18:35 ` Christoph Anton Mitterer
2010-07-25 15:28 ` Arno Wagner
2010-07-25 18:11 ` Milan Broz
2010-07-26 9:04 ` Mario 'BitKoenig' Holbe
2010-07-27 18:21 ` Christoph Anton Mitterer
2010-07-27 21:02 ` Mario 'BitKoenig' Holbe
2010-07-26 9:17 ` Mario 'BitKoenig' Holbe
2010-07-27 18:42 ` David Santamaría Rogado
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=4C721FEA.4020705@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
/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