xfs
[Top] [All Lists]

Re: power failure .. broken files.. broken FS :(.

To: Daniel Palmer <danielpalmer@xxxxxxxxxxxxx>
Subject: Re: power failure .. broken files.. broken FS :(.
From: Net Llama! <netllama@xxxxxxxxxxxxx>
Date: Mon, 5 Jan 2004 15:52:58 -0500 (EST)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1073335468.1440.12.camel@rei>
References: <1073335468.1440.12.camel@rei>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Mon, 5 Jan 2004, Daniel Palmer wrote:
> I had a power failure a couple days ago, didn't think anything about it
> and continued using my system as normal until all but 2 files in a
> directory didn't want to open in xmms this morning.
[SNIP]
> Phase 7 - verify and correct link counts...
> corrupt dinode 44179985, extent total = 1, nblocks = 0.  Unmount and run
> xfs_repair.
> fatal error -- couldn't map inode 44179985, err = 990
>
> The files I couldn't access are now gone (to where no one knows) but
> they're of little importance. But I get the same output everytime and
> get no further :(, lost+found is also empty but running find on the fs
> presented this "find: ./_torrents/chobits_7_1024.jpg: Unknown error
> 990".

I'm pretty sure that you have to manually delete lost+found
(from the partition where you're running xfs_repair) after each run of
xfs_repair.  Othewise, it just keeps repairing the same stuff over & over
again.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                                netllama@xxxxxxxxxxxxx
Linux Step-by-step & TyGeMo                  http://netllama.ipfox.com


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