From: Hans Reiser <reiser@namesys.com>
To: "Ihar 'Philips' Filipau" <filia@softhome.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ReiserFS causing kernel panic?
Date: Mon, 13 Oct 2003 09:28:51 +0400 [thread overview]
Message-ID: <3F8A3813.7070503@namesys.com> (raw)
In-Reply-To: <3F89D567.6080901@softhome.net>
Ihar 'Philips' Filipau wrote:
> Hans Reiser wrote:
>
>> reiserfs is not warranted to work on corrupted hdds.....
>
>
> Is there any kind of error statistics for hard drives?
>
> Geometry is known.
> I suspect that structure of damages, caused by contact of plates
> surface with head, can be classified.
>
>
> It may be possible to classify manufacturing glitches. I think HD
> producers have this kind of classification/statistics - to improve
> quality, keeping price low.
>
> Actually what I'm thinking of: some kind of design rules for file
> systems, how to minimize crashing due to hdd glitches.
> Let's say, if some of hdd regions are know to be more error prone -
> desing fs to use those regions less.
> If hdd damages used to have some specific structure - design file
> system to keep renundant data in regions which are less likely to be
> lost both at the same time. So renundancy would make sense.
>
> Is there any thing like this?
>
> Or file systems now do outlive hard drives?-)
>
Block allocation policies affect performance a lot, and keeping them
simple is important. I would however be interested in knowing what
the distribution function for errors by geometry is. If it turned out
that, say, errors were higher at the platter edges, I could make some
format changes....
I think that for users it is best to think about how to mask drive
errors in the device layer or the device using RAID and mirroring.
--
Hans
next prev parent reply other threads:[~2003-10-13 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FNmF.1ky.9@gated-at.bofh.it>
[not found] ` <FNFZ.1JI.3@gated-at.bofh.it>
[not found] ` <FP59.3H0.17@gated-at.bofh.it>
[not found] ` <FVkc.42S.5@gated-at.bofh.it>
2003-10-12 22:27 ` ReiserFS causing kernel panic? Ihar 'Philips' Filipau
2003-10-13 5:28 ` Hans Reiser [this message]
2003-10-12 12:13 Promise Ultra133-TX2 (PCD20269) Mark Williams (MWP)
2003-10-12 12:28 ` Måns Rullgård
2003-10-12 14:00 ` ReiserFS causing kernel panic? Mark Williams (MWP)
2003-10-12 14:32 ` Tomas Szepe
2003-10-12 16:24 ` Mark Williams (MWP)
2003-10-13 7:13 ` Hans Reiser
2003-10-12 20:42 ` Hans Reiser
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=3F8A3813.7070503@namesys.com \
--to=reiser@namesys.com \
--cc=filia@softhome.net \
--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