From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] VFS prior to 1984
Date: Sun, 5 Jul 2020 14:40:06 -0400 [thread overview]
Message-ID: <238b6e06-b6d9-20b0-a4d2-ed1207e3168a@kilonet.net> (raw)
In-Reply-To: <20200705144332.GR29318@mcvoy.com>
On 7/5/2020 10:43 AM, Larry McVoy wrote:
> So I've encountered lots of holes in NFS files where there shouldn't be
> any. So it is/was a thing. But that said, I can't remember a single
> case of encountering that on Sun's campus. I don't know if my memory
> is failing me, but I do know that when I left Sun and started working
> with other NFS implementations, yeah, lots of problems. Somehow Sun
> got it right where other people didn't.
I can say personally, since the early 90's on SunOS, I never ever saw
this problem in a variety of environments. One being Nynex Science and
Technology where I did a consulting stint. 800+ node Sun 3/4 SunOS
workstation/server environment, basically everyone's desktop was a Sun
workstation for email, documentation, whatever. Another being a defense
contractor I was at for 7 years, they were all Sun for engineering
workstations and servers.
There is one possibility I just thought of, and that's if the first
write fails and then a context switch happens, if enough free space is
made available before the next context switch back to the second write,
I can see that being a problem ;)
As if you weren't already tired of my rambling... When it comes to
non-Sun operating systems, all bets were off. They all (mostly) worked
with their own kind. That usually wasn't the case when it came to
cross-vendor support. Sun<->HP was not great, but that also may have
been driver problems in the one instance I tried it for an extended
period of time. Two instances at different customers of AIX<->Sun
actually worked rather well. The YP integration was key.
The entire problem with "holey" files and NFS is certainly related to
the usage type of the system in question. What was Sun doing? Email?
Software development? Using a common NFS share for the compiler? And
then copying their code up to a central location? Not a lot of
sync/write/sync/write activity, unless object file generation is a lot
of skipping around all over the place. ;)
art k.
next prev parent reply other threads:[~2020-07-05 18:41 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
2020-07-05 14:43 ` Larry McVoy
2020-07-05 18:40 ` Arthur Krewat [this message]
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=238b6e06-b6d9-20b0-a4d2-ed1207e3168a@kilonet.net \
--to=krewat@kilonet.net \
--cc=tuhs@minnie.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).