From owner-freebsd-bugs Mon Oct 21 23:53:09 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA05468 for bugs-outgoing; Mon, 21 Oct 1996 23:53:09 -0700 (PDT) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA05463; Mon, 21 Oct 1996 23:53:06 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id CAA07733; Tue, 22 Oct 1996 02:52:14 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.7.3) with ESMTP id CAA25471; Tue, 22 Oct 1996 02:50:59 -0400 (EDT) To: Peter Wemm cc: Heikki Suonsivu , FreeBSD-gnats@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org From: "Gary Palmer" Subject: Re: kern/1698: sup from around 21:51 GMT 28th very unstable (mmap, maybe?) In-reply-to: Your message of "Tue, 22 Oct 1996 14:43:23 +0800." <199610220643.OAA10951@spinner.DIALix.COM> Date: Tue, 22 Oct 1996 02:50:58 -0400 Message-ID: <25469.845967058@orion.webspan.net> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter Wemm wrote in message ID <199610220643.OAA10951@spinner.DIALix.COM>: > 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 el > se > . > > > > sup from 20th october still bad, panic within 24 hours (news+nfs), > > filesystems get badly corrupted (lots of dup/bad inodes, zero-length direct > or > 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... :-( Just FYI, our news box here, 20Gb stripe, has had 0 filesystem corruption as a result of kernel troubles (a disk teetering on the edge of death did corrupt the FS tho :-( ). Done from a CVS co about a month or so ago. 4K FS blocksize. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info