From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Hans Reiser <reiser@namesys.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ReiserFS causing kernel panic?
Date: Mon, 13 Oct 2003 00:27:51 +0200 [thread overview]
Message-ID: <3F89D567.6080901@softhome.net> (raw)
In-Reply-To: <FVkc.42S.5@gated-at.bofh.it>
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?-)
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
--
"... and for $64000 question, could you get yourself vaguely
familiar with the notion of on-topic posting?"
-- Al Viro @ LKML
next parent reply other threads:[~2003-10-12 22:27 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 ` Ihar 'Philips' Filipau [this message]
2003-10-13 5:28 ` ReiserFS causing kernel panic? Hans Reiser
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=3F89D567.6080901@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/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