[667] in NetBSD-Development
Re: AFS bug??
daemon@ATHENA.MIT.EDU (John Hawkinson)
Tue Mar 14 19:16:24 1995
Date: Tue, 14 Mar 1995 19:15:40 -0500
To: yoav@MIT.EDU
Cc: jhawk@MIT.EDU, netbsd-dev@MIT.EDU
In-Reply-To: "[666] in NetBSD-Development"
From: John Hawkinson <jhawk@MIT.EDU>
> wow.. that was long..
Better too long than too short...
> in short. mycroft observed a similar thing (though much more minor).
> I suspect there is some sort of HD corruption occuring somewhere,
> and my guess would be not by AFS, but by something lower
> level.
How could cache corruption make listing a directory not possible?
Further, how would this cause garbage in the console window?
> Anyway, doing an fs flushvol worked for mycroft, and I'd suspect it
> would work in this case too, though we should find out how this
> corruption happened,
Tried that. It made things work (but it caused more console messages:
19:09 >^E~xbrowser^A
19:09 @^Exinfo.help^A
19:09 ^B^Fxinfo.text.help^A?^D^BRCSbrowser^A
19:09 %^binbsdbin^A^AM^F binin^A^E decmipsbin^A%^An^Z^Rbackup_index^A^Knextbinlp^A
19:09 olc_browserelp^A^A?^F^Aps2binn^A^AQ^F/rsaixbin^AG^xrtbinin^A^K^P^F1sparcbinwers^AI^zstock_answers^A^_^AO^F-sun4bin^A^}^Dvaxbin^A/%^wlinuxbin^A^A^v^Zthe_job~^A^C^^W;.#olc-stock
> (and somebody should -- just in case -- log in as root and delete
> the cachefiles). yoav
Huh? You mean shutdown, boot single user, clean the cache, and restart?
Or something else?
--jhawk
