I believe that you need to purge the contents of lost+found after running
xfs_repair, or it will keep trying to repair the same thing over & over
again. So purge (or at least move) the contents of lost+found, then run
On Thu, 9 Sep 2004, Anastas Giokov wrote:
> After a disk problem (bad sectors) I have the following problem:
> Using xfs_repair on the device I receive the following message:
> corrupt inode XXXXX (btree). Unmount and run xfs_repair.
> fatal error -- 990 - couldn't iget disconnected inode
> The device is unmounted at this point and re-running xfs_repair dives the
> same output. The resulting fs is mountable, but part of it is not recovered.
> Is there a way to "skip" the corrupt inode, so the repair can finish, even
> losing some data?
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
Lonni J Friedman netllama@xxxxxxxxxxxxx
Linux Step-by-step & TyGeMo http://netllama.ipfox.com