Path: utzoo!attcan!uunet!husc6!bloom-beacon!apple!well!pokey From: pokey@well.UUCP (Jef Poskanzer) Newsgroups: comp.unix.aux Subject: Re: Some notes on problems in A/UX Message-ID: <6836@well.UUCP> Date: 17 Aug 88 18:38:42 GMT References: <5123@hoptoad.uucp> Reply-To: Jef PoskanzerOrganization: Paratheo-Anametamystikhood Of Eris Esoteric, Ada Lovelace Cabal Lines: 21 In the referenced message, hugh@hoptoad.uucp (|-|ugh Daniel) wrote: } (Question: Has anyone else run into cases where fsck finds a } problem, reboots, then finds ANOTHER problem so bad it has to } reboot a second time? I have seen this in A/UX and never } elsewhere.) When I was using pre-release A/UX, I would typically reboot once or twice a day. fsck would find and fix a problem about on about half of these reboots. Maybe once in two weeks, it would do a double reboot as you describe above. And twice in N months, it went into continuous reboots. fsck would claim to have fixed the problem, reboot, and then do exactly the same thing again. When I showed this to a wizard he mumbled something about fsck not flushing all its buffers -- sounds pretty dangerous to me! Anyway, I haven't used A/UX since it was released, and I assumed all these problems were fixed. Apparently not. --- Jef Jef Poskanzer jef@rtsg.ee.lbl.gov ...well!pokey It's hard to see the forest when you're one of the trees.