From owner-freebsd-fs Sat Mar 2 21:29: 5 2002 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9495B37B400 for ; Sat, 2 Mar 2002 21:29:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g235Stc59042; Sat, 2 Mar 2002 21:28:55 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Mar 2002 21:28:55 -0800 (PST) From: Matthew Dillon Message-Id: <200203030528.g235Stc59042@apollo.backplane.com> To: Kris Kennaway Cc: Ian Dowse , Kris Kennaway , Kirk McKusick , Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org :-- :I restarted the bento build with the 4.x package set, after upgrading :the gohans to 4.5-STABLE (one of them had panicked with ffs_alloc: dup :alloc). I also set up the gohans to scrub their disks at boot time. :-- : :Prior to this, I think they were running 4.4-STABLE as of about Nov :25, which was the last time I upgraded them. I don't think I've seen :a recurrence of the dup alloc panic lately, so this might have been :fixed between November and January. : :Combined with the alpha kernels running from around Jan 26 this seems :to narrow the range a fair bit. : :Kris The date range needs to be narrowed down on a single machine if possible. A lot of changes were made between January 26th and February 10th: cd /usr/src/sys cvs diff -j RELENG_4:20020125 -j RELENG_4:20020211 * device polling was added to a couple of ethernet drivers * changes to usb were made * changes to vinum * i386 cr0 boot-time initialization changed * changes to the floppy driver * changes to the timecounter * maxusers auto-sizing calculation changed * changes to aio * changes to kern.maxvnodes handling * VOP_INACTIVE MFC * WRITECLOSE flushing - now also flushes out unlinked but still open files. * route socket interface announcements were added * ip_input / ip_output changes * bootp changes. * minor nfs changes * FFS mount downgrade to read-only fix MFC * various softupdates fixes Also, when you get it narrowed down, see if the kern.maxvnodes setting has an effect (e.g. normal verses something large like 9999999). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message