public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: different behaviour with badblocks on 2.6.0-test1-mm1-07int
Date: Wed, 23 Jul 2003 12:32:47 -0700	[thread overview]
Message-ID: <20030723193247.GI1176@matchmail.com> (raw)
In-Reply-To: <20030723190929.GB1288@home.woodlands>

On Thu, Jul 24, 2003 at 12:39:29AM +0530, Apurva Mehta wrote:
> * Mike Fedyk <mfedyk@matchmail.com> [2003-07-23 22:41]:
> > > I am using 2.1.14.. Still no luck with it reading disks.. 
> > 
> > Maybe you need to mount sysfs on /sys?
> 
> Right, gkrellm does report some disk usage now, but it is far from
> accurate. It registers barely any of the disk activity. Starting
> Firebird or Opera may occasionally register one spike on the
> graph. Mostly, the disk activity is not reported. 
> 
> This seems to be a gkrellm bug since vmstat reports disk usage more
> accurately, although I haven't really looked closely at the output..

Ok let's forget about gkrellm because I see similar numbers in vmstat.

Now, let's get back to the origional issue, which is "Why the fuck is
badblocks reading when it should only be writing, and why does it only
happen on a 2.6-test kernel?!!"

      reply	other threads:[~2003-07-23 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 21:42 different behaviour with badblocks on 2.6.0-test1-mm1-07int Mike Fedyk
2003-07-22 21:45 ` 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 [this message]

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=20030723193247.GI1176@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