From mboxrd@z Thu Jan 1 00:00:00 1970 From: ron@ronnatalie.com (Ron Natalie) Date: Thu, 11 May 2017 18:30:07 -0400 Subject: [TUHS] The evolution of Unix facilities and architecture In-Reply-To: <20170511222547.GJ4341@mcvoy.com> References: <20170511140729.2262B18C09A@mercury.lcs.mit.edu> <013b01d2ca96$6901b370$3b051a50$@ronnatalie.com> <20170511222547.GJ4341@mcvoy.com> Message-ID: <015901d2caa6$2594b410$70be1c30$@ronnatalie.com> I got a phone call one day from one of the operators that "fsck was stuck in a loop." I thought maybe it was wedged or it was just printing out continuously. I got there and find that Fsck had repaired the root partition and rebooted the machine and then come up and decided the root needed fixing again and then rebooted... The operator didn't mention that the "fsck loop" involved a reboot every time through. The other one I got was that "fsck has been printing for an hour." After getting them to read me one of the errors I suggested they scroll back the printout and find the first message. RP01 OFFLINE. Now, go over to the disk drive and look in the glass top and tell me...is it spinning? No? Now put the run/stop switch to stop. Now put it to Run. Now reboot the machine and DON'T LEAN ON THE FRONT OF THE DRIVE AGAIN. (This one RP06 if you leaned on the lid it would spin down the disk).