Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!tgr!sienkiew@UDEL-DEWEY.ARPA
From: sienkiew@UDEL-DEWEY.ARPA
Newsgroups: net.unix
Subject: Re: root fsck dups
Message-ID: <10840@brl-tgr.ARPA>
Date: Mon, 20-May-85 11:37:43 EDT
Article-I.D.: brl-tgr.10840
Posted: Mon May 20 11:37:43 1985
Date-Received: Tue, 21-May-85 04:46:54 EDT
Sender: news@brl-tgr.ARPA
Lines: 32


>Can an application program or broken utility like passwd create this mess or
>must this result from a kernel or hardware failure?

Application programs that directly play with the disk can do this.  This
is limited to things like clri, icheck, dcheck, & fsck.  passwd should
not be able to do it.  I hesitate to say cannot, since I've seen what
weird things some unixes do*, but there should be no way for a normal
application to cause this.

>Dups rarely occur on /usr or /tmp and seem to appear on / during peak periods.

Do you run the fscks during peak periods too?  If you do, you may be seeing
totally garbaged data, since the file system will be changing faster than
fsck could follow (if it even tried...).

I've noticed weird things happen to unix file systems under these conditions:
1- somebody took down the system without a sync.  Or they cause a panic.
   Either way, everything is automatically suspect.
2- I only work on small machines, so I don't always remember to go to single
   user mode before checking the fs.  Then uucp logs in and I get a dozen
   diagnostics.  (This cleared up a lot when I quit doing this.)

What more can you tell us about your systems, in particular, what do you
have that isn't 100% vanilla?


			Mark.

---
* i.e. HPUX csh puts your terminal in cbreak so it can fake newcrt without
putting it in the kernel.  I kid you not.