xfs
[Top] [All Lists]

fatal error -- xfs_repair: duplicate inode range

To: linux-xfs@xxxxxxxxxxx
Subject: fatal error -- xfs_repair: duplicate inode range
From: Michael Best <mbest@xxxxxxxxxxxxx>
Date: Sun, 17 Mar 2002 22:44:39 -0700
Sender: owner-linux-xfs@xxxxxxxxxxx
I was called Sunday morning for a machine that had failed.

You could ping it from the network but nothing else.

I rebooted it, and got a XFS Page alloc kernel panic I believe. (unsure
it's been hours since then).

I rebooted it in single user mode, read some logfiles and then rebooted it
into multi user mode.

A short while later the machine appeared to fail again, when rebooted it
could no longer load the initrd in order to mount the root (/) filesystem
to boot.

I used a Mandrake 8.2rc1 disc to boot the system, after finding the mount
command on the 1.0.2 installer disc was hopeless.

I ran XFS repair, which suggested something good had happened.  And then it
suggested mounting it.  No luck.  It suggested I could use xfs_repair -L to
try and mount it after that.

I tried that, no luck.  All further attempts produce output like this: 

fatal error -- xfs_repair:  duplicate inode range

Here are the logs from xfs_check and xfs_repair for this filesystem.

http://www.emergence.com/xfs_trouble/xfs_check_sda5.txt
http://www.emergence.com/xfs_trouble/xfs_repair_sda5.txt

The machine was originally running a single Quantum Atlas V on Ultra 160
Scsi chain.  I have moved this machine to two Maxtor 20G drives with Raid 1
mirroring.  The Scsi chain is still in the machine with the broken
filesystem drive and I can make it available/prepare a filesystem dump
(perhaps someone can explain how to do that).  Hopefully I have enough
space on my drive for that.

I saw other people with this error in the mailing list archives but didn't
see if there was a solution to this problem.

I should be available by 10am Pacific 12pm Eastern on Monday March 18th,
2002.

--
Michael Best
Emergence By Design
+1 780 413-6397


<Prev in Thread] Current Thread [Next in Thread>