From owner-freebsd-current Sat Mar 17 11: 6:45 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 45C5C37B719 for ; Sat, 17 Mar 2001 11:06:43 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2HJ5se95038; Sat, 17 Mar 2001 11:05:54 -0800 (PST) (envelope-from dillon) Date: Sat, 17 Mar 2001 11:05:54 -0800 (PST) From: Matt Dillon Message-Id: <200103171905.f2HJ5se95038@earth.backplane.com> To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: Panic and filesystem corruption References: <200103150039.f2F0drt33628@earth.backplane.com> <200103160144.f2G1ijO53569@earth.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt Dillon writes: :> 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? : :Umm, the end of the cvsup log was padded with zeroes, but I don't :think that qualifies as file corruption. As far as I could see, no :files were damaged - only one of the gnats subdirectories. : :DES :-- :Dag-Erling Smorgrav - des@ofug.org Good. Oh, I take it back... one of the earlier bug reports did report file corruption, but it may have been due to something else or related to the directory corruption. How fast a link was the cvsup running through? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message