From: Pavel Machek <pavel@suse.cz>
To: Daniel Phillips <phillips@innominate.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advanced Linux Kernel/Enterprise Linux Kernel
Date: Mon, 20 Nov 2000 13:34:23 +0000 [thread overview]
Message-ID: <20001120133423.A221@toy> (raw)
In-Reply-To: <200011141459.IAA413471@tomcat.admin.navo.hpc.mil> <3A117311.8DC02909@holly-springs.nc.us> <news2mail-3A15ACE3.5BED2CA3@innominate.de> <20001118164021.A156@toy> <news2mail-3A183A01.4F214A4F@innominate.de>
In-Reply-To: <news2mail-3A183A01.4F214A4F@innominate.de>; from news-innominate.list.linux.kernel@innominate.de on Sun, Nov 19, 2000 at 09:37:21PM +0100
Hi!
> > > Actually, I was planning on doing on putting in a hack to do something
> > > like that: calculate a checksum after every buffer data update and check
> > > it after write completion, to make sure nothing scribbled in the buffer
> > > in the interim. This would also pick up some bad memory problems.
> >
> > You might want to take look to a patch with crc loop option.
> >
> > It does verify during read, not during write; but that's even better because
> > that way you pick up problems in IO subsystem, too.
>
> You would have to store the checksums on the filesystem then, or use a
I store checksums in separate partition.
> verify-after-write. What I was talking about is a
> verify-the-buffer-didn't get scribbled. I'd then trust the hardware to
> report a write failure. Note that if something scribbles on your buffer
> between the time you put good data on it and when it gets transfered to
> disk, you can verify perfectly and still have a hosed filesystem.
Actually, I have 50% chance detecting that corruption. If it happens
between application and loop, I detect nothing. If it happens between
loop and disk, I catch it.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-20 23:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 14:59 Advanced Linux Kernel/Enterprise Linux Kernel Jesse Pollard
2000-11-14 15:47 ` David Weinehall
2000-11-14 17:14 ` Michael Rothwell
2000-11-14 16:20 ` Mike Dresser
2000-11-14 17:27 ` Michael Rothwell
2000-11-14 17:32 ` Michael Rothwell
2000-11-14 16:25 ` Richard B. Johnson
2000-11-14 17:29 ` Michael Rothwell
2000-11-14 16:38 ` Mark Hahn
2000-11-14 19:23 ` spam
2000-11-14 16:41 ` Richard B. Johnson
2000-11-14 17:06 ` Michael Meissner
2000-11-14 17:59 ` Richard B. Johnson
2000-11-14 17:51 ` Buddha Buck
2000-11-14 18:10 ` Michael Rothwell
2000-11-14 18:00 ` Richard B. Johnson
2000-11-15 0:31 ` Gerhard Mack
2000-11-14 20:08 ` Alexander Viro
2000-11-14 16:57 ` David Relson
2000-11-14 18:17 ` Rik van Riel
2000-11-14 19:15 ` spam
2000-11-14 16:53 ` David Relson
2000-11-14 17:06 ` Andrea Arcangeli
2000-11-14 17:55 ` Andreas Dilger
2000-11-14 18:35 ` Christoph Hellwig
2000-11-14 23:06 ` Werner Almesberger
2000-11-15 4:25 ` Albert D. Cahalan
2000-11-17 22:10 ` Daniel Phillips
2000-11-18 0:58 ` Eric W. Biederman
2000-11-18 20:13 ` Daniel Phillips
2000-11-18 16:40 ` Pavel Machek
2000-11-19 20:37 ` Daniel Phillips
2000-11-20 13:34 ` Pavel Machek [this message]
2000-11-14 17:34 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 5:28 Bernd Eckenfels
2000-11-15 4:19 Marty Fouts
2000-11-14 18:20 Marty Fouts
2000-11-14 18:18 Marty Fouts
2000-11-14 18:10 Marty Fouts
2000-11-14 19:43 ` Steve VanDevender
2000-11-15 1:13 ` Leo Mauro
2000-11-14 18:06 Marty Fouts
2000-11-14 18:03 Marty Fouts
2000-11-08 20:31 [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI) richardj_moore
2000-11-13 21:56 ` Advanced Linux Kernel/Enterprise Linux Kernel Josue Emmanuel Amaro
2000-11-14 7:49 ` Lars Marowsky-Bree
2000-11-14 18:33 ` lamont
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=20001120133423.A221@toy \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
/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.