Date: Wed, 17 Mar 1999 09:34:36 +1030 From: Greg Lehey <grog@lemis.com> To: Roelof Osinga <roelof@eboa.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Have crashed, won't travel Message-ID: <19990317093436.G429@lemis.com> In-Reply-To: <36EE54A4.8DC53017@eboa.com>; from Roelof Osinga on Tue, Mar 16, 1999 at 01:55:00PM %2B0100 References: <36DCB59E.F16D5539@eboa.com> <19990303195632.B441@lemis.com> <36DDBFEB.86D89D20@eboa.com> <19990304095813.I441@lemis.com> <36DDEFFD.A4DB4978@eboa.com> <19990304130126.B441@lemis.com> <36DE0352.E99BCB70@eboa.com> <19990316174710.H429@lemis.com> <36EE54A4.8DC53017@eboa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 16 March 1999 at 13:55:00 +0100, Roelof Osinga wrote: > Greg Lehey wrote: >> >> This junk is the record of what you entered to the visual UserConfig. >> The gibberish are control codes for the terminal emulation. > > I see, thanks. Wouldn't have expected it in a log, but I guess it makes > sense for crash determination purposes. I suspect it's just because it was easier that way. >> Well, XENIX had a pretty typical old-style file system layout. ufs is >> better, and doesn't get so corrupted. >> >> You can assume that's OK. It isn't always, but I've seen very very >> few instances of file system damage which wasn't detected by fsck. > > Both are good to hear. The more so since I've experienced yet > another crash. Since things like that wreck havock with my schedule > I've changed the NIC I suspect to be the cause. Hasn't crashed since > which I see as a good sign <g>. > > This time I got some more interesting messages like (only the good > parts): > > /dev/rwd0s1g (= /usr): UNKNOWN FILETYPE I=644 > UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY > > (I'm not shouting, I'm quoting verbatim :) Yup, I know, fsck shouts. > INCORRECT BLOCK COUNT I=645/646/647 > > FREE BLK COUNT(S) WRONG IN SUPERBLOCK SALVAGE? > SUMMARY INF. BAD > BLK(S) MISSING IN BIT MAPS > > which lead to this: > > root:/usr/local/etc/cvsup# ls /usr/ports/devel/crossgo32/pkg/ > CVS DESCR PLIST > root:/usr/local/etc/cvsup# cat /usr/ports/devel/crossgo32/pkg/PLIST > cat: /usr/ports/devel/crossgo32/pkg/PLIST: Device not configured > root:/usr/local/etc/cvsup# cat /usr/ports/devel/crossgo32/pkg/DESCR > cat: /usr/ports/devel/crossgo32/pkg/DESCR: Device not configured > root:/usr/local/etc/cvsup# ls /usr/ports/devel/ddd/ > CVS Makefile README.html files pkg This looks like relatively serious file system damage. I'd guess that one of these files has its inode corrupted (and it makes it look like a device file). The best thing you can do here is to completely remove the directory: # rm -fr /usr/ports/devel/crossgo32/pkg/ and then re-create it by whatever method you used to create it in the first place. It's conceivable that you might have a panic while trying to do this, so do a sync first and don't have anything else running while you do. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990317093436.G429>