From owner-freebsd-current Thu Jul 2 02:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16108 for freebsd-current-outgoing; Thu, 2 Jul 1998 02:47:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16102 for ; Thu, 2 Jul 1998 02:47:29 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id KAA00578 for ; Thu, 2 Jul 1998 10:47:24 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <359B572C.EFD5C099@tdx.co.uk> Date: Thu, 02 Jul 1998 10:47:24 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Filesystem corruption? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been running -current for a while, the last make world I did was 21/6/98. The systems been running fine, I had a couple of panic's over the last few months - but just recently I've been going to load files and found them corrupt... Things like: c---rw---x 844382393/478298378 54 Apr 17 13:21 mezon.config Doing an rm gets: rm c---rw---x 844382393/478298378, nochg, unlnk, sunlnk? Followed by: operation not permitted. Any further attempts to remove the file just get: operation not permitted. Some files also get random corruption in them... The filesystem is IDE based - I'm not using async or softupdates etc, just plain old mount defaults... Has anyone seen anything like this? Are there any 'stress' tests I can do on this filesystem? (something a little less risky/more informative than make worlds?) - the drive as it stands has /usr/obj mounted on it, but the source for the makeworlds is on another SCSI... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message