home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!udecc.engr.udayton.edu!blackbird.afit.af.mil!dsacg3.dsac.dla.mil!dsacg4.dsac.dla.mil!nol2321
- From: nol2321@dsacg4.dsac.dla.mil (Jim Dunn)
- Newsgroups: comp.protocols.nfs
- Subject: Re: duplicate files in NFS directory under heavy load?
- Message-ID: <5805@dsacg4.dsac.dla.mil>
- Date: 12 Jan 93 15:40:54 GMT
- References: <1993Jan10.052211.7018@siswat.hou.tx.us> <un9r06k@rhyolite.wpd.sgi.com> <davecb.726758667@yorku.ca>
- Organization: Defense Logistics Agency Systems Automation Center, Columbus
- Lines: 17
-
-
- > This is noticable when doing a ``rename(2v)'' on a systems which
- >does not give the appearance of atomaticity. This is easy to demonstrate
- >on an overloaded sun3 (:-))
- > With FFS, you say ``mv foo bar'' and for a brief period there is an entry for
- >both foo and bar: the creation of bar is atomic, but the deletion of foo
- >only appears atomic to the caller. Other processes reading the directory
- >can aften see both foo abd bar for a brief period over NFS.
-
- I've got a BETTER one for yuh! If you use PC-NFS with a Gould Unix box,
- and turn the *sticky* bit on and then do a mv.exe or use Norton's Commander
- or Directory Freedom to rename a directory... you'll get TWO entries with
- the SAME I-Node FOREVER!!!
-
- Yuck!
- :-<
- Jim
-