From owner-freebsd-questions Fri Jun 7 21:29:40 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04839 for questions-outgoing; Fri, 7 Jun 1996 21:29:40 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA04824 for ; Fri, 7 Jun 1996 21:29:36 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA02616; Fri, 7 Jun 1996 22:29:26 -0600 Date: Fri, 7 Jun 1996 22:29:26 -0600 From: Nate Williams Message-Id: <199606080429.WAA02616@rocky.sri.MT.net> To: Gary Kline Cc: cslye@info.infosite.com (Cameron Slye), questions@freebsd.org Subject: Re: lockups In-Reply-To: <199606080358.UAA13381@athena.tera.com> References: <199606070413.VAA00249@info.infosite.com> <199606080358.UAA13381@athena.tera.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ CSLIP/PPP lockups ] > I figured that there might be some inconsistancy in the > filesystem. > > Long-story-short: fsck'ing everything found that my /var > fs was damaged. It's been a day or two since I did the > fs check and clean. So far, so good. > > You might want to try doing a number of fsck runs until > everything is *clean*. Reboot and see if the lockup > problem reoccurs. Note, fsck(8) in stable has a known bug that requires multiple passes in order to completely cleanup the FS. This bug appears to be fixed in -current with a patch Terry Lambert submitted, but since I'm not FS guru I won't vouch that I *completely* understand the fix. That's the reason it's in -current and not -stable, but if it's any consolation all of my boxes are running with this patch on them. :) Nate