From owner-freebsd-current Thu Mar 15 17:45:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4A99137B719 for ; Thu, 15 Mar 2001 17:45:19 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2G1ijO53569; Thu, 15 Mar 2001 17:44:45 -0800 (PST) (envelope-from dillon) Date: Thu, 15 Mar 2001 17:44:45 -0800 (PST) From: Matt Dillon Message-Id: <200103160144.f2G1ijO53569@earth.backplane.com> To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: Panic and filesystem corruption References: <200103150039.f2F0drt33628@earth.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt Dillon writes: :> How old a kernel are you running? : :Maybe five days old. : :DES :-- :Dag-Erling Smorgrav - des@ofug.org That has all of our fixes to date. It fits the M.O. of the problem I've been trying to track down, but I have yet to be able to reproduce the problem consistently. It's good to know that you were cvsup'ing GNATS and it didn't previously exist. That helps a little. We still haven't been able to narrow it down as to whether the bug is related to softupdates or not. If you have time and can run cvsup/rm-rf in a loop, it would be interesting to see if you can reproduce the crash reliably. cvsup's basic operation is to create directories, then for each file it creates the file under a temporary name, writes it out, closes, and then renames it. At the moment I am focusing on the rename operation as being the possible culprit, but no smoking gun has been found yet. To date nearly all the reported corruption has been to directories and not to file contents. Does this hold for you as well? Only the directory was corrupted and not any files? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message