From owner-freebsd-bugs Tue Oct 22 09:05:11 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07542 for bugs-outgoing; Tue, 22 Oct 1996 09:05:11 -0700 (PDT) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA07530; Tue, 22 Oct 1996 09:05:03 -0700 (PDT) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.6/8.6.4) with ESMTP id SAA26212; Tue, 22 Oct 1996 18:05:00 +0200 (EET) Received: (hsu@localhost) by katiska.clinet.fi (8.7.6/8.6.4) id TAA04027; Tue, 22 Oct 1996 19:04:58 +0300 (EET DST) Date: Tue, 22 Oct 1996 19:04:58 +0300 (EET DST) Message-Id: <199610221604.TAA04027@katiska.clinet.fi> From: Heikki Suonsivu To: Peter Wemm Cc: Heikki Suonsivu , FreeBSD-gnats@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1698: sup from around 21:51 GMT 28th very unstable (mmap, maybe?) In-Reply-To: <199610220643.OAA10951@spinner.DIALix.COM> References: <199610220516.IAA00811@katiska.clinet.fi> <199610220643.OAA10951@spinner.DIALix.COM> Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter Wemm writes: > Heikki Suonsivu wrote: > > > > Heikki Suonsivu writes: > > > FreeBSD-gnats@freefall.freebsd.org writes: > > > > Thank you very much for your problem report. > > > > It has the internal identification `kern/1698'. > > > > The individual assigned to look at your > > > > bug is: freebsd-bugs. > > > > > > > > >Category: kern > > > > >Responsible: freebsd-bugs > > > > >Synopsis: sup from around 21:51 GMT 28th very unstable (mmap, ma > ybe?) > > > > >Arrival-Date: Mon Sep 30 21:10:01 PDT 1996 > > > > > > Crashes without mmap also; apparently the problem has to be somewhere else > . > > > > sup from 20th october still bad, panic within 24 hours (news+nfs), > > filesystems get badly corrupted (lots of dup/bad inodes, zero-length director > y, > > usually sequential inodes get killed). > > Are you using a 4K blocksize on your news file system by any chance? I've > been having corruption problems like this for 12 months now, and changing > to 8K blocks seems to have cured it.. (at least, the machine has been up > for 7 days now, previous record was 3 and a half days). The disk > overheads are a killer though... :-( We use 4K blocksize. With the previous kernel from about a month a go we have been getting uptimes of about a week, I do not know for sure how much average would be as I have been about once a week tried to upgrade to a newer current. I haven't seen a single corruption problem with that kernel, though some panics, so something bad happened about month ago. We mount some thing from the news server with NFS, so it might be related to other people reporting NFS being flakey for last couple of weeks. The filesystem corruption is nasty, as it requires manual care to get things up and going... > > > Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi > > > mobile +358-40-5519679 work +358-0-43542270 fax -4555276 home -8031121 > > Cheers, > -Peter -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-43542270 fax -4555276