From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File System Corruption with 2.2.18
Date: Thu, 18 Jan 2001 10:38:09 +0200 [thread overview]
Message-ID: <20010118103809.P1265@niksula.cs.hut.fi> (raw)
In-Reply-To: <Pine.LNX.4.30.0101180035080.28099-100000@pine.parrswood.manchester.sch.uk> <Pine.LNX.4.10.10101171645110.19441-200000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10101171645110.19441-200000@master.linux-ide.org>; from andre@linux-ide.org on Wed, Jan 17, 2001 at 05:14:02PM -0800
On Wed, Jan 17, 2001 at 05:14:02PM -0800, you [Andre Hedrick] claimed:
> On Thu, 18 Jan 2001, Tim Fletcher wrote:
>
> > > Well that is useless test them because you can not test things completely.
> >
> > I ment that if the partiton has no persient data on it then the test can
> > be run (the test wipes all data on the partition out during the test,
> > right?) with no loss of data on the machine. The partition is still on the
> > same disk so the test data is valid?
> >
> > I am thinking that the test is somewhat like badblocks -w or have I got
> > the wrong end of the stick?
>
> Sorry there is no stick to get the end of....
> This is a pure diagnostic tool the determine OS/CHIPSET/DEVICE failures.
> You generate a pattern buffer and write it to the disk and step the buffer
> 1 byte per sector and go head to tail. Then you read it back head to tail
> and compare what should be there with what is there. Failures == FS
> corruption is likely under highest loads, period. Then you attempt
> to extract any patterns or periodic events to determine if it is driver or
> device or other portions of the OS.
>
> I am tired of people pointing the finger at me claim my work is the cause
> of FS corruption.
>
> This is a pattern walk and it will give some performance issue.
> It does not care about the OS, it is doing the direct access that some
> would call bit-bangging in the old days.
But it works on all ATA disks? Does it work for SCSI as well?
I think it would be cool if you'd make it available (on linux-ide.org?),
so that people install servers (and anybody who _cares_) could test their
hardware/driver combination before starting using the box.
Now we have memtest86, cpuburn (what more). It would be nice to have a
good (if not complete) test set to run on each new linux box. It's not
nice to use the box for a month and then go "f..., this box has faulty
memory!" or ..."faulty disk!". Yes, that's what's happened to all of us.
It's much nicer to get a warranty replacement, when you don't have any
data on the disk.
-- v --
v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 17:48 Terrence Martin
2001-01-17 18:06 ` Andre Hedrick
2001-01-17 18:32 ` Vojtech Pavlik
2001-01-17 18:40 ` Andre Hedrick
2001-01-17 18:46 ` Vojtech Pavlik
2001-01-17 22:44 ` Andre Hedrick
2001-01-17 23:57 ` Tim Fletcher
2001-01-18 0:32 ` Andre Hedrick
2001-01-18 0:39 ` Tim Fletcher
2001-01-18 1:14 ` Andre Hedrick
2001-01-18 8:38 ` Ville Herva [this message]
2001-01-18 8:45 ` Andre Hedrick
2001-01-18 8:52 ` Ville Herva
2001-01-17 18:53 ` Terrence Martin
2001-01-17 19:03 ` Vojtech Pavlik
2001-01-18 17:15 ` Terrence Martin
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=20010118103809.P1265@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--cc=andre@linux-ide.org \
--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
all inboxes | Powered by JetHome®