Date: Thu, 15 Mar 2001 17:44:45 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: current@FreeBSD.ORG Subject: Re: Panic and filesystem corruption Message-ID: <200103160144.f2G1ijO53569@earth.backplane.com> References: <xzp8zm91d5a.fsf@flood.ping.uio.no> <200103150039.f2F0drt33628@earth.backplane.com> <xzpr8zydg54.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
:Matt Dillon <dillon@earth.backplane.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103160144.f2G1ijO53569>