From: Hans Reiser <reiser@namesys.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Norman Diamond <ndiamond@wta.att.ne.jp>,
Wes Janzen <superchkn@sbcglobal.net>,
Rogier Wolff <R.E.Wolff@BitWizard.nl>,
John Bradford <john@grabjohn.com>,
linux-kernel@vger.kernel.org, nikita@namesys.com,
Pavel Machek <pavel@ucw.cz>,
Justin Cormack <justin@street-vision.com>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Vitaly Fertman <vitaly@namesys.com>,
Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: Blockbusting news, results are in
Date: Sun, 19 Oct 2003 12:08:00 +0400 [thread overview]
Message-ID: <3F924660.4040405@namesys.com> (raw)
In-Reply-To: <20031019041553.GA25372@work.bitmover.com>
Larry McVoy wrote:
>
>
>I've told you guys over and over that you need to CRC the data in user
>space, we do that in our backup scripts and it tells us when the drives
>are going bad. S
>
Why do the CRC in user space, that requires modifying every one of 7000+ applications (if I understand you correctly, which is far from a sure thing;-) )?
Write a reiser4 CRC file plugin. It would take a weekend, and most of the work would be cut and pasting from the default file plugin..
I understand why you do it in BK, but for user space as a whole user space is the wrong place.
next prev parent reply other threads:[~2003-10-19 8:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 2:16 Blockbusting news, results are in Norman Diamond
2003-10-19 4:15 ` Larry McVoy
2003-10-19 5:00 ` Paul
2003-10-19 8:19 ` Andre Hedrick
2003-10-19 8:08 ` Hans Reiser [this message]
2003-10-19 8:35 ` William Lee Irwin III
2003-10-19 20:01 ` Pavel Machek
2003-10-19 20:11 ` William Lee Irwin III
2003-10-20 7:24 ` John Bradford
2003-10-19 22:49 ` jw schultz
2003-10-20 7:22 ` John Bradford
2003-10-20 8:22 ` jw schultz
2003-10-20 7:27 ` Hans Reiser
2003-10-20 8:08 ` jw schultz
2003-10-19 19:49 ` Pavel Machek
2003-10-20 7:22 ` Hans Reiser
2003-10-21 10:31 ` Eric W. Biederman
2003-10-21 8:43 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2003-10-19 7:37 Mudama, Eric
2003-10-19 8:09 ` Norman Diamond
2003-10-19 8:24 ` Hans Reiser
2003-10-19 11:43 ` Ralf Baechle
2003-10-19 15:55 ` Krzysztof Halasa
2003-10-19 8:13 ` Rogier Wolff
2003-10-19 8:17 ` Hans Reiser
2003-10-19 8:41 ` Rogier Wolff
2003-10-20 15:56 ` Thayne Harbaugh
2003-10-19 8:21 ` Andre Hedrick
2003-10-19 8:27 ` Hans Reiser
2003-10-19 9:01 ` Erik Andersen
2003-10-19 14:10 ` Andre Hedrick
2003-10-19 18:16 ` Hans Reiser
2003-10-19 19:44 ` Andre Hedrick
2003-10-20 7:21 ` Hans Reiser
2003-10-19 14:42 ` Valdis.Kletnieks
2003-10-19 10:47 ` Ingo Oeser
2003-10-19 17:36 Mudama, Eric
2003-10-19 17:39 Mudama, Eric
2003-10-19 17:51 Mudama, Eric
2003-10-20 6:22 ` Rogier Wolff
2003-10-20 14:08 Mudama, Eric
2003-10-20 14:42 ` John Bradford
2003-10-20 15:55 Mudama, Eric
2003-10-20 17:32 ` Hans Reiser
2003-10-21 15:18 Norman Diamond
2003-10-21 19:31 ` Chuck Campbell
2003-10-21 20:05 ` Richard B. Johnson
2003-10-21 20:21 ` Valdis.Kletnieks
2003-10-21 20:31 ` Richard B. Johnson
2003-10-21 21:53 ` Theodore Ts'o
2003-10-22 2:32 ` Valdis.Kletnieks
2003-10-23 17:28 ` Theodore Ts'o
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=3F924660.4040405@namesys.com \
--to=reiser@namesys.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=ndiamond@wta.att.ne.jp \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@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;
as well as URLs for NNTP newsgroup(s).