xfs
[Top] [All Lists]

Re: Partition un(mount|repairable)

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Partition un(mount|repairable)
From: Jason White <jasonjgw@xxxxxxxxxxxxxx>
Date: Fri, 11 Jan 2002 12:43:08 +1100
In-reply-to: <3C3C45F2.D6533E44@cs.tum.edu>
References: <3C3C45F2.D6533E44@cs.tum.edu>
Reply-to: Jason White <jasonjgw@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Deti Fliegl writes:
 > Hi
 > 
 > some days ago one of our systems crashed due to a defective CPU cooler.
 > The XFS filesystem on it now is unmountable and unrepairable:
 > 
 > ....
 > imap claims in-use inode 686650 is free, correcting imap
 > imap claims in-use inode 686651 is free, correcting imap
 > imap claims in-use inode 686652 is free, correcting imap
 > imap claims in-use inode 686653 is free, correcting imap
 > imap claims in-use inode 686654 is free, correcting imap
 > imap claims in-use inode 686655 is free, correcting imap
 > avl_insert: Warning! duplicate range [0xbee40,0xbee80)
 > 
 > fatal error -- xfs_repair:  duplicate inode range

Any suggestions as to how the damage was done in the first place -
what the bug is?

There have been worrying reports of data corruption over the last few
weeks, and I am sure the developers are trying to track them down. My
own system hasn't been used much recently as I have been away on
holiday, but I booted it this morning and everything seemed fine
(running Linux 2.4.17-xfs as downloaded from CVS at the end of last
year).


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