From: Tom Vier <tmv@comcast.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Plugin for corruption resistance?
Date: Fri, 11 Feb 2005 15:53:50 -0500 [thread overview]
Message-ID: <20050211205350.GA13345@zero> (raw)
In-Reply-To: <e692861c05021110583585f84e@mail.gmail.com>
On Fri, Feb 11, 2005 at 01:58:59PM -0500, Gregory Maxwell wrote:
> 1. Lots of applications today (such a P2P sharing systems) need the
> hashes of files.. it's inefficient to keep recomputing them. The file
> system always knows when a file changes, so it can be setup to always
> return the correct hash.
That should be done in userland, imho. Especially since different apps use
lots of different hashes.
I was thinking about this kind of stuff (ECC plugin for r4) not too long
ago. Hashing the whole file is too slow; if you update a single block, the
whole file has to be read in to recalculate. Adding, say, one sector of crc
for each block would be a lot more feasible.
I think the best way to do this though, would be to write a virtual blk
driver that works like loop back (ie, uses a backing file/dev), and shortens
the overall size by one sector * number of blocks. Actually, you could
probably copy the raid5 md code and rewrite it to only use one device. I'd
try that first.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
next prev parent reply other threads:[~2005-02-11 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 18:58 Plugin for corruption resistance? Gregory Maxwell
2005-02-11 20:39 ` Jake Maciejewski
2005-02-11 20:53 ` Tom Vier [this message]
2005-02-12 5:19 ` David Masover
2005-02-13 3:48 ` Esben Stien
2005-02-14 2:01 ` Reiser 4 Apple Michael James
2005-02-14 18:49 ` Hans Reiser
2005-02-14 17:45 ` Plugin for corruption resistance? Hans Reiser
2005-02-15 20:42 ` Adam
2005-02-17 4:10 ` David Masover
2005-02-17 10:53 ` Christian Iversen
2005-02-18 3:43 ` David Masover
2005-02-18 4:28 ` Valdis.Kletnieks
2005-02-18 13:36 ` Gregory Maxwell
2005-02-18 22:09 ` Valdis.Kletnieks
2005-02-19 3:28 ` Gregory Maxwell
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=20050211205350.GA13345@zero \
--to=tmv@comcast.net \
--cc=gmaxwell@gmail.com \
--cc=reiserfs-list@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 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.