From owner-freebsd-current Mon May 21 10:59:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id A79A637B43F; Mon, 21 May 2001 10:59:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4LHwiG45078; Mon, 21 May 2001 10:58:45 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B05E8BE.8AE0CD29@camtech.net.au> Date: Mon, 21 May 2001 10:58:50 -0700 (PDT) From: John Baldwin To: Matthew Thyer Subject: Re: background fsck Cc: chris@aims.com.au, mckusick@FreeBSD.org, current@FreeBSD.org, Jason Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-May-01 Matthew Thyer wrote: > Is it possible that background fsck is not the culprit here ? I think > this may be fallout from the dirpref changes as Chris Knight recently > emailed in <018b01c0c496$07ed13d0$020aa8c0@aims.private>. The solution > is to unmount all your filesystems, fsck them and then use tunefs with > -A to change something so that all superblock backups will be updated. > > Does this sound likely ? > > Jason Evans wrote: >> >> I had exactly the same thing happen to /var on an SMP test box using >> -current as of 16 May. It happened once out of about a half dozen panics. >> >> Jason My instances at least are not the result of dirpref, as my laptop tracks -current very closely and I navigated the dirpref waters a while back. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message