From: David Masover <ninja@slaphack.com>
To: Edward Shishkin <edward@namesys.com>
Cc: Tom Reinhart <rhino_tom@hotmail.com>, reiserfs-list@namesys.com
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org
Date: Tue, 15 Aug 2006 18:29:05 -0500 [thread overview]
Message-ID: <44E258C1.4020403@slaphack.com> (raw)
In-Reply-To: <44E24E46.6070106@namesys.com>
Edward Shishkin wrote:
> David Masover wrote:
>> Edward Shishkin wrote:
>>
>>> Tom Reinhart wrote:
>>>
>>>> Anyone with serious need for data integrity already uses RAID, so
>>>> why add brand new complexity for a solved problem?
>>>>
>>>> RAID is great at recovering data, but not detecting errors. File
>>>> system can detect errors with checksum. What is missing is an API
>>>> between layers for filesystem to say "this sector is bad, go rebuild
>>>> it."
>>>>
>>>
>>> Actually we dont need a special API: kernel should warn and recommend
>>> running fsck, which scans the whole tree and handles blocks with bad
>>> checksums.
>>
>>
>> What does this have to do with RAID, though?
>>
>>
>
> I assumed we dont have raid: reiser4 can support its own checksums/ecc
> signatures for (meta)data protection via node plugin
We don't have a guaranteed raid, however, it would be nice to do the
right thing when there is raid.
next prev parent reply other threads:[~2006-08-15 23:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 21:27 the " 'official' point of view" expressed by kernelnewbies.org Tom Reinhart
2006-08-15 21:55 ` Hans Reiser
2006-08-15 22:06 ` Edward Shishkin
2006-08-15 22:20 ` Hans Reiser
2006-08-16 2:34 ` Tom Reinhart
2006-08-16 3:29 ` Gregory Maxwell
2006-08-15 22:27 ` David Masover
2006-08-15 22:44 ` Edward Shishkin
2006-08-15 23:29 ` David Masover [this message]
2006-08-16 1:14 ` Gregory Maxwell
2006-08-16 4:23 ` Hans Reiser
2006-08-16 15:08 ` Ric Wheeler
2006-08-16 22:48 ` Hans Reiser
2006-08-24 16:11 ` PFC
2006-08-16 2:53 ` Tom Reinhart
-- strict thread matches above, loose matches on Subject: below --
2006-07-24 15:57 Al Boldi
2006-07-24 17:43 ` Horst H. von Brand
2006-07-24 18:46 ` H. Peter Anvin
2006-07-25 4:07 ` Matthew Frost
2006-07-25 4:57 ` Al Boldi
2006-07-25 5:03 ` Jeff Garzik
2006-07-25 8:33 ` the ' 'official' point of view' " Luigi Genoni
2006-07-25 14:35 ` the " 'official' point of view" " Horst H. von Brand
2006-07-25 15:14 ` Lexington Luthor
2006-07-25 20:59 ` Matthias Andree
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=44E258C1.4020403@slaphack.com \
--to=ninja@slaphack.com \
--cc=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rhino_tom@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.