From: John Bradford <john@grabjohn.com>
To: skraw@ithnet.com (Stephan von Krawczynski)
Cc: john@grabjohn.com (John Bradford),
vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: Are linux-fs's drive-fault-tolerant by concept?
Date: Mon, 21 Apr 2003 13:04:31 +0100 (BST) [thread overview]
Message-ID: <200304211204.h3LC4VA6000616@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <20030421130341.06d60830.skraw@ithnet.com> from "Stephan von Krawczynski" at Apr 21, 2003 01:03:41 PM
> > Name an IDE or SCSI disk on sale today that doesn't retry on write
> > failiure. Forget I said 'Generally do'.
>
> IBM DMVS18V (SCSI)
> Maxtor ATA133 160 GB DiamondMax Plus.
>
> Maybe they _should_, but I can tell you they in fact sometimes don't
> (IBM very, very seldom, Maxtor just about all the time)
How do you know those disks don't retry on write failiure? How do you
know they aren't retrying and failing?
> How do _you_ know that? What makes _you_ argue for what _I_ think is
> useful and _my_ sense of security? You are on thin ice ...
Linux is an open source operating system, you are welcome to add the
feature if you want it.
> > We have moved on since the 1980s, and I believe that it is now up to
> > the drive firmware, or the block device driver to do this, it has no
> > place in a filesystem.
>
> Interestingly I owned one of those 30 MB MFM Seagate howling drives
> back in the 80s. I had no errors on it until I threw it away for its
> unbelievable noise rate. Today I throw away one (very low-noise)
> disk about every week for shooting yet another fs somewhere near
> midnight.
> Indeed we moved on, only the direction looks sometimes questionable ...
Ask the disk manufacturers for advice.
John.
next prev parent reply other threads:[~2003-04-21 11:50 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 16:04 Are linux-fs's drive-fault-tolerant by concept? Stephan von Krawczynski
2003-04-19 15:29 ` Alan Cox
2003-04-19 17:00 ` Stephan von Krawczynski
2003-04-19 22:04 ` Alan Cox
2003-04-20 16:24 ` Stephan von Krawczynski
2003-04-20 13:59 ` John Bradford
2003-04-20 16:55 ` Stephan von Krawczynski
2003-04-20 17:12 ` John Bradford
2003-04-20 17:21 ` Stephan von Krawczynski
2003-04-20 18:48 ` Alan Cox
2003-04-20 20:00 ` John Bradford
2003-04-21 1:51 ` jw schultz
2003-04-19 21:13 ` Jos Hulzink
2003-04-20 16:07 ` Stephan von Krawczynski
2003-04-20 16:40 ` John Bradford
2003-04-20 17:01 ` Stephan von Krawczynski
2003-04-20 17:20 ` John Bradford
2003-04-21 9:32 ` Stephan von Krawczynski
2003-04-21 9:55 ` John Bradford
2003-04-21 11:24 ` Stephan von Krawczynski
2003-04-21 11:50 ` Alan Cox
2003-04-21 12:14 ` John Bradford
2003-04-19 16:22 ` John Bradford
2003-04-19 16:36 ` Russell King
2003-04-19 16:45 ` John Bradford
2003-04-19 16:52 ` Stephan von Krawczynski
2003-04-19 20:04 ` John Bradford
2003-04-19 20:33 ` Andreas Dilger
2003-04-21 9:25 ` Denis Vlasenko
2003-04-21 9:42 ` John Bradford
2003-04-21 10:25 ` Stephan von Krawczynski
2003-04-21 10:50 ` John Bradford
2003-04-19 20:38 ` Stephan von Krawczynski
2003-04-20 14:21 ` John Bradford
2003-04-21 9:09 ` Denis Vlasenko
2003-04-21 9:35 ` John Bradford
2003-04-21 11:03 ` Stephan von Krawczynski
2003-04-21 12:04 ` John Bradford [this message]
2003-04-21 11:22 ` Denis Vlasenko
2003-04-21 11:46 ` Stephan von Krawczynski
2003-04-21 12:13 ` John Bradford
2003-04-19 20:05 ` John Bradford
2003-04-19 23:13 ` Arnaldo Carvalho de Melo
2003-04-19 17:54 ` Felipe Alfaro Solana
2003-04-25 0:07 ` Stewart Smith
2003-04-25 0:52 ` Richard B. Johnson
2003-04-25 7:13 ` John Bradford
[not found] ` <20030419161011$0136@gated-at.bofh.it>
2003-04-19 17:18 ` Florian Weimer
2003-04-19 18:07 ` Stephan von Krawczynski
2003-04-19 18:41 ` Dr. David Alan Gilbert
2003-04-19 20:56 ` Helge Hafting
2003-04-19 21:15 ` Valdis.Kletnieks
2003-04-20 10:51 ` Helge Hafting
2003-04-20 19:04 ` Valdis.Kletnieks
2003-04-19 21:57 ` Alan Cox
2003-04-20 10:09 ` Geert Uytterhoeven
2003-04-21 8:37 ` Denis Vlasenko
2003-05-05 12:38 ` Pavel Machek
2003-04-19 22:02 ` Alan Cox
2003-04-20 8:41 ` Arjan van de Ven
2003-04-25 0:11 ` Stewart Smith
2003-04-20 15:06 Chuck Ebbert
2003-04-20 15:19 ` John Bradford
2003-04-20 17:03 Chuck Ebbert
2003-04-20 17:25 ` John Bradford
2003-04-20 17:28 Chuck Ebbert
2003-04-21 9:36 ` Stephan von Krawczynski
2003-04-20 17:28 Chuck Ebbert
2003-04-20 17:44 Chuck Ebbert
2003-04-20 17:44 Chuck Ebbert
[not found] <mail.linux.kernel/20030420185512.763df745.skraw@ithnet.com>
[not found] ` <03Apr21.020150edt.41463@gpu.utcc.utoronto.ca>
2003-04-21 11:19 ` Stephan von Krawczynski
2003-04-21 11:52 ` Alan Cox
2003-04-21 14:14 ` Valdis.Kletnieks
2003-05-06 7:03 ` 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=200304211204.h3LC4VA6000616@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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;
as well as URLs for NNTP newsgroup(s).