Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 23 Feb 2003 12:48:23 -0800 (PST) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1NKmH3v003710 for ; Sun, 23 Feb 2003 12:48:18 -0800 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id h1NKvDoT015140; Sun, 23 Feb 2003 12:57:13 -0800 From: "l.a walsh" To: "'Russell G. Howe'" , Subject: RE: xfs_repair unable to repair a corrupt filesystem Date: Sun, 23 Feb 2003 12:57:13 -0800 Message-ID: <000501c2db7e$240eff00$1403a8c0@sc.tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20030223081255.GA14077@lithium.sta.man.ac.uk> X-archive-position: 2864 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xfs@tlinx.org Precedence: bulk X-list: linux-xfs Content-Length: 1943 Lines: 57 Seems that xfs_repair isn't very robust -- it doesn't even detect the problem on my disk that causes xfsdump to knock my rootfs offline. :-( -l > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com] On Behalf Of Russell G. Howe > Sent: February 23, 2003 12:13a > To: linux-xfs@oss.sgi.com > Subject: xfs_repair unable to repair a corrupt filesystem > > > Hi, > > I'm having some problems with /var on my machine. The machine > itself is > rather unstable and hangs every few days, but I don't think that is > XFS-related. > > What does concern XFS is the data corruption I experience after such a > hard lockup (Alt+SysRq+B won't reboot the box, no HDD activity, etc). > /var has had at least some corruption for the past week or so which I > haven't had chance to fix. I took the opportunity just now after the > latest hang (which has hosed /home). I'll post a seperate > message about > the /home problem singe it seems to be a seperate issue. > > xfs_repair on /var appeared to fix at least some things, but > there were > clearly still errors. I re-ran xfs_repair and got this output: > http://rhowe.sfarc.net/xfs_repair_var.txt.gz The output appears identical no matter how many times I run xfs_repair. I'm using XFS from CVS, sometime around the 19th Dec (that is the date of compilation, and I update just before I compile). It's based on 2.4.20. Is this too old to be of use as a bug report? I am able and willing to build a more up to date release of XFS if need be. xfs_repair is from the Debian (unstable) package, and reports its version as 2.3.11 I can mount /var, but all those xfs_repair errors make me rather suspicious about using it. Most errors appear to be centred around one large (700Mbish) file, which I don't mind losing. -- Russell Howe | Why be just another cog in the machine, rhowe@wiss.co.uk | when you can be the spanner in the works?