From owner-freebsd-current Thu Jul 2 07:04:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26176 for freebsd-current-outgoing; Thu, 2 Jul 1998 07:04:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (root@ts01-55.waterford.indigo.ie [194.125.139.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26167 for ; Thu, 2 Jul 1998 07:04:43 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id OAA00699; Thu, 2 Jul 1998 14:53:59 +0100 (IST) (envelope-from rotel@ginseng.indigo.ie) From: Niall Smart Message-Id: <199807021353.OAA00699@indigo.ie> Date: Thu, 2 Jul 1998 14:53:59 +0000 In-Reply-To: Karl Pielorz "Filesystem corruption?" (Jul 2, 10:47am) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Filesystem corruption? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 2, 10:47am, Karl Pielorz wrote: } Subject: Filesystem corruption? > > 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... Looks like either your disk is hosed or the filesystem on it is corrupt. Use chflags chg,nounlnk,nosunlnk mezon.config before trying to remove it (see chflags(1)). Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message