Date: Tue, 22 Jul 2003 15:15:33 -0700
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: different behaviour with badblocks on 2.6.0-test1-mm1-07int
Message-ID: <20030722221533.GF1176@matchmail.com>
Mail-Followup-To: linux-kernel@vger.kernel.org
References: <20030722214253.GD1176@matchmail.com> <20030722214557.GE1176@matchmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030722214557.GE1176@matchmail.com>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1435
Lines: 36

On Tue, Jul 22, 2003 at 02:45:57PM -0700, Mike Fedyk wrote:
> On Tue, Jul 22, 2003 at 02:42:53PM -0700, Mike Fedyk wrote:
> > 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                  
> > 
> 
> Oh, and testing with the same hardware and userspace on 2.4.22-pre7 shows
> normal behaviour (writes with no reading, reads with no writing).
> 
> This is with "badblocks -wso /tmp/hde.out /dev/hde > /dev/hde.log 2>&1 &" on
> a bash prompt on both kernels.
> 
> Neither found any bad blocks, and /tmp is on a /dev/hda1
> 

This is also being reported against e2fsprogs in debian to get more eyes on
it.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202008
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/