From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] VFS prior to 1984
Date: Sat, 4 Jul 2020 21:43:04 -0400 [thread overview]
Message-ID: <CAC20D2OW2vwR+uzkSSoMk5kvZKzwQXXnYDsAwmaOgxygy_dfFQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007050939520.455@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Sat, Jul 4, 2020 at 8:07 PM Dave Horsfall <dave@horsfall.org> wrote:
> Aren't holes part of the file system semantics?
>
Exactly - and that was the problem with NFS. Consider two write
operations. Remember each op is a complete operation with a seek to where
it's going. If the first fails, but the error is not reported (NFS returns
errors on close), the second operations seek over the failed write -- UNIX
puts zeros in the file. File closes later and the size is fine of
course. Oh yeah, whoever bothered to check for errors on close (like the
traditional SCCS or RCS commands)?
Later to try to read your file back -- it will have a bunch of zeros.
As Larry says, running a simple checksum could catch a lot of these.
Anyway, I'm going to be good and lay off a diatribe on NFS. It sort of
worked 'good enough.' But I will say other systems (like AFS) were much
better, in practice, but it lost the war.
Clem
[-- Attachment #2: Type: text/html, Size: 2056 bytes --]
next prev parent reply other threads:[~2020-07-05 1:44 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:09 Paul Ruizendaal
2020-06-23 14:01 ` Larry McVoy
2020-06-23 15:12 ` Clem Cole
2020-06-23 15:55 ` Rich Morin
2020-06-23 20:38 ` Rob Pike
2020-06-23 20:57 ` Larry McVoy
2020-06-24 5:14 ` arnold
2020-06-24 21:08 ` Dave Horsfall
2020-06-24 19:30 ` Clem Cole
2020-06-24 19:36 ` Larry McVoy
2020-06-25 6:52 ` Rob Gingell
2020-07-05 0:05 ` Dave Horsfall
2020-07-05 0:16 ` Larry McVoy
2020-07-06 4:42 ` Dave Horsfall
2020-07-06 16:51 ` Chris Torek
2020-07-06 23:23 ` [TUHS] ECC memory John Gilmore
2020-07-07 1:07 ` [TUHS] VFS prior to 1984 Bakul Shah
2020-07-05 1:43 ` Clem Cole [this message]
2020-07-05 14:43 ` Larry McVoy
2020-07-05 18:40 ` Arthur Krewat
2020-07-05 20:08 ` Clem Cole
2020-07-05 20:42 ` John Cowan
2020-07-05 21:04 ` Clem Cole
2020-07-05 21:14 ` Dan Cross
2020-06-24 16:51 ` Anthony Martin
2020-06-24 17:31 ` Anthony Martin
2020-06-24 18:31 ` Paul Ruizendaal
2020-06-25 0:56 ` Rob Gingell via TUHS
2020-06-25 4:15 ` [TUHS] Oh, things were very different Rich Morin
2020-06-25 15:45 ` Lawrence Stewart
2020-06-25 16:24 ` Warner Losh
2020-06-25 17:57 ` Arthur Krewat
2020-06-25 20:22 ` Dave Horsfall
2020-06-25 20:42 ` Michael Kjörling
2020-06-25 20:49 ` Clem Cole
2020-06-26 0:48 ` Dave Horsfall
2020-06-24 19:05 ` [TUHS] VFS prior to 1984 Paul Ruizendaal
2020-06-24 20:27 ` Derek Fawcus
2020-06-24 21:33 ` Greg A. Woods
2020-06-25 0:45 ` Adam Thornton
2020-06-25 19:40 ` Greg A. Woods
2020-06-23 22:17 Norman Wilson
2020-06-23 22:24 ` Dave Horsfall
2020-06-24 4:09 ` Warner Losh
2020-06-24 5:10 ` Dave Horsfall
2020-06-24 5:33 ` Bakul Shah
2020-06-24 9:10 ` Andrew Warkentin
2020-06-24 14:31 Noel Chiappa
2020-06-24 15:21 ` Clem Cole
2020-06-24 17:51 Noel Chiappa
2020-06-24 18:13 ` Richard Salz
2020-06-24 18:46 ` Lars Brinkhoff
2020-06-24 18:31 Norman Wilson
2020-06-25 6:22 ` arnold
2020-06-25 19:31 Noel Chiappa
2020-06-25 20:23 Noel Chiappa
2020-06-25 20:25 Noel Chiappa
2020-06-26 5:49 ` Lars Brinkhoff
2020-06-26 8:34 ` Dave Horsfall
2020-06-26 11:13 ` arnold
2020-06-29 9:11 Paul Ruizendaal
2020-06-29 14:45 ` Larry McVoy
2020-06-29 14:53 ` Paul Ruizendaal
2020-06-29 15:14 ` Larry McVoy
2020-06-29 16:34 ` Heinz Lycklama
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=CAC20D2OW2vwR+uzkSSoMk5kvZKzwQXXnYDsAwmaOgxygy_dfFQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/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).