From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: different behaviour with badblocks on 2.6.0-test1-mm1-07int
Date: Tue, 22 Jul 2003 14:42:53 -0700 [thread overview]
Message-ID: <20030722214253.GD1176@matchmail.com> (raw)
Hi,
I was testing a hard drive with badblocks (from the e2fsprogs-1.34) on the
2.6.0-test1-mm1-07int (with Con's scheduler patch), and I noticed in vmstat
and gkrellm that during the write passes there are reads on the same drive
when there should only be writes.
I tried stracing badblocks, but all it showed was write() calls, and vmstat
and gkrellm showed reads only, so it modified the behaviour.
Has anyone else seen this?
ii e2fsprogs 1.33+1.34-WIP-2003.05 The EXT2 file system
utilities and libraries
next reply other threads:[~2003-07-22 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 21:42 Mike Fedyk [this message]
2003-07-22 21:45 ` different behaviour with badblocks on 2.6.0-test1-mm1-07int Mike Fedyk
2003-07-22 22:15 ` Mike Fedyk
2003-07-23 8:18 ` Apurva Mehta
2003-07-23 13:24 ` Valdis.Kletnieks
2003-07-23 15:19 ` Apurva Mehta
2003-07-23 17:01 ` Mike Fedyk
2003-07-23 19:09 ` Apurva Mehta
2003-07-23 19:32 ` Mike Fedyk
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=20030722214253.GD1176@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
/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