Date: Sat, 2 Mar 2002 21:28:55 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Ian Dowse <iedowse@maths.tcd.ie>, Kris Kennaway <kris@obsecurity.org>, Kirk McKusick <mckusick@mckusick.com>, Finch <dot@dotat.at>, fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk Subject: Re: UFS panic on -stable Message-ID: <200203030528.g235Stc59042@apollo.backplane.com> References: <20020302135914.A33051@xor.obsecurity.org> <200203022233.aa08277@salmon.maths.tcd.ie> <20020302144532.A33433@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:--
: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203030528.g235Stc59042>