louis@asterix.drev.dnd.ca (Louis Demers) (03/22/90)
We are experiencing disappearing partitions. In an effort to understand what is happening, we ran fsck on / and got the following after the phase. LINK COUNT TABLE OVERFLOW CONTINUE ? If we answer yes, the same message appears again. If we answer no, it quits. What is wrong ? Louis PS: A prompt reply would be appreciated as we have contractors waiting for a fix before they continue their work. -- | Louis Demers | DREV, Defence Research Establishment,Valcartier | | louis@asterix.drev.dnd.ca | POBox 8800, Courcelette,Quebec, CANADA, G0A 1R0 | | (131.132.48.2) | Office: (418) 844-4424 fax (418) 844-4511 | +---------------------------+-------------------------------------------------+
davism@creatures.cs.vt.edu (Mat Davis) (03/23/90)
In article <1990Mar22.155559.25638@asterix.drev.dnd.ca> louis@asterix.drev.dnd.ca (Louis Demers) writes: >We are experiencing disappearing partitions. In an effort to >understand what is happening, we ran fsck on / and got >the following after the phase. > >LINK COUNT TABLE OVERFLOW >CONTINUE ? > >If we answer yes, the same message appears again. If we answer >no, it quits. I've seen this once on one of my machines; if you keep answering 'y' many, many times the fsck will eventually finish, but then it will reboot the machine and the same thing will happen. After going through this cycle about six times, everything finally cleared up (just keep typing 'y'). To speed the entire process, you can run fsck from sash to avoid the overhead of launching A/UX, doing the fsck, and then rebooting over and over. Mat
dumais@nixter.UUCP (Paul E. Dumais) (03/23/90)
In article <206@creatures.cs.vt.edu> davism@creatures.cs.vt.edu (Mat Davis) writes: > In article <1990Mar22.155559.25638@asterix.drev.dnd.ca> louis@asterix.drev.dnd.ca (Louis Demers) writes: > >We are experiencing disappearing partitions. In an effort to > >understand what is happening, we ran fsck on / and got > >the following after the phase. [deleted] > I've seen this once on one of my machines; if you keep answering 'y' many, > many times the fsck will eventually finish, but then it will reboot the > machine and the same thing will happen. After going through this cycle > about six times, everything finally cleared up (just keep typing 'y'). > > To speed the entire process, you can run fsck from sash to avoid the > overhead of launching A/UX, doing the fsck, and then rebooting over and > over. > > Mat You will save your right index finger any your "Y" key if you type fsck -y /dev/rdsk/c0d0s0 which answers YES to all of the questions that arise. Mat is correct that running this from the SASH (or A/UX Startup 2.0) incures much less overhead. -ped- -- -------------------------------------------------------------------------- | Paul E. Dumais:A/UX Specialist:Apple Canada Inc.:+1 416 474-9872 | | "Where *does* he get those wonderful toys - The Joker" | --------------------------------------------------------------------------