From owner-freebsd-current Thu Dec 3 21:14:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20461 for freebsd-current-outgoing; Thu, 3 Dec 1998 21:14:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20453 for ; Thu, 3 Dec 1998 21:14:52 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id VAA68094; Thu, 3 Dec 1998 21:22:46 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812040522.VAA68094@troutmask.apl.washington.edu> Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: from Alfred Perlstein at "Dec 3, 1998 11:10: 8 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Thu, 3 Dec 1998 21:22:46 -0800 (PST) Cc: kuehn@rz.tu-clausthal.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alfred Perlstein: > > dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var > > panic: ffs_blkfree: bad size > > > > The /var filesystem does not have soft updates enabled. > > I got a dump, but not from a debugging kernel. > > > > [ current as of Dec 2 ] > > Just wondering, why are people running softupdates and non-softupdates on > the same box, or just plain not using softupdates? > > I thought that it is as reliable as regular mounts and faster? Or are > there issues that I haven't noticed? > > Or are you guys testing for the FreeBSD project? > Well, FFS with sync mounts has been reliable for me for 4 years until this commit. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message