Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-adm!brl-smoke!smoke!es!David_Weisman%anvil.UUCP@harvard.harvard.edu
From: David_Weisman%anvil.UUCP@harvard.harvard.edu
Newsgroups: net.unix-wizards
Subject: Network filosofy question?
Message-ID: <2383@brl-smoke.ARPA>
Date: Fri, 4-Apr-86 20:06:38 EST
Article-I.D.: brl-smok.2383
Posted: Fri Apr  4 20:06:38 1986
Date-Received: Wed, 9-Apr-86 07:50:09 EST
Sender: news@brl-smoke.ARPA
Lines: 13


I am curious about how people have implemented networked file
systems (RFS, NFS, others) to handle inode refcounts (di_nlink).
Specifically, how do these systems insure refcount integrity
over network or node failures, and what if anything can fsck do
to rebuild the refcounts when some of the links originate from
other nodes/filesystems?

If anyone is awake, I'll summarize and post.  Thanks very much.

David Weisman
ihnp4!anvil!weisman
(617) 460-