Message-ID: <3D5A3174.1A91A496@up.ac.za>
Date: Wed, 14 Aug 2002 12:31:16 +0200
From: Paul Schutte <paul@up.ac.za>
MIME-Version: 1.0
To: XFS mailing list <linux-xfs@oss.sgi.com>
Subject: Problem repairing filesystem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

Background:
----------------

I ran a ftp server on a pentium II 333Mhz with 256M RAM, using the
2.4.9-31-xfs kernel.
Used 4 x 120 Gb IDE drives in a RAID 5 array on an Adaptec 2400 hardware
raid controller.
There is a 4Gb root partition and a +/- 320Gb data partition.

One of the drives failed and the machine crashed.
We replaced the drive and rebuild the array.


I booted up with a CD that I created a while a go with
2.4.19-pre9-20020604 and mounted a
nfs root partition with all the xfs tools on it.
We ran xfs_repair (version 2.2.1) on the root partition of the raid
array.
A lot of the files have the dreaded zero problem, but apart from that it
is mountable and usable.

The problem:
------------------

We ran xfs_repair on the 320Gb partition.

After about 15min xfs_repair died with 'Terminated' being print on the
console.

dmesg reveals:
Out of Memory: Killed process 269 (xfs_repair).

I recreated the swap partition and activated it.

Ran xfs_repair again.

<xfs_repair>
--snip--
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - ensuring existence of lost+found directory
        - traversing filesystem starting at / ...
        - traversal finished ...
        - traversing all unattached subtrees ...

fatal error -- can't read block 0 for directory inode 2097749
</xfs_repair>

When you mount the filesystem, it is empty (except for lost+found which
is also empty)

The output of xfs_repair is large about 300k bzip2'ed. It would be best
if interested parties download it.

http://www2.up.ac.za/paul/xfs_repair.out.bz2

http://www2.up.ac.za/paul/dmesg.out.bz2

Questions:
--------------
Have I lost the 320G partition or does someone still have a trick up
their sleeve ?

Would it be possible to make xfs_repair use a lot less memory ?
My guess is that the filesystem got it's final blow by xfs_repair
exiting prematurely.


Any suggestions are welcome.

Paul Schutte