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!dgladden@wsmr08.ARPA
From: dgladden@wsmr08.ARPA (Doug Gladden CD-SP)
Newsgroups: net.unix
Subject: root fsck dups
Message-ID: <10808@brl-tgr.ARPA>
Date: Sat, 18-May-85 13:53:50 EDT
Article-I.D.: brl-tgr.10808
Posted: Sat May 18 13:53:50 1985
Date-Received: Sun, 19-May-85 06:43:51 EDT
Sender: news@brl-tgr.ARPA
Lines: 13

Recently, we've been plagued with our nightly fsck reporting two inodes
claiming to own the same duplicate block on the root file system on several of
our BBN C70 System V machines with 167M Ampex drives.

/etc/wtmp or even worse /etc/passwd are often involved, resulting in a lot of
effort in cleaning up the filesystem and recreating the files.

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

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

Thanks in advance for any help you can offer.