On Thu, Nov 27, 2003 at 10:14:22AM +0200, Tomi Orava wrote:
>
> Hi,
>
> I received the following error message last night, which obviously
> resulted lots of problems while running xfs_repair, as the xfs_repair
> was unable to get some inodes fixed properly, even though the repair
> command was ran several times. In the end I found that the problematic
> inodes belong to some directories which had been already moved to
> lost+found directory and by renaming and the old lost+found
> directory to other name and recreating the dir finally fixed those problems.
> However, the xfs_repair still complains about "rebuilding directory inode
> 128" which belongs to "/" ... That one is still not fixed.
Not clear what caused the original problem (h/ware or s/ware)
but it looks like xfs_repair has fixed things up for you --
128 will be your root inode, and it will continually be rebuilt
when you run repair if you don't remove "/lost+found" between
each invocation. For more details see the archives, eg:
http://marc.theaimsgroup.com/?l=linux-xfs&m=102981254408403&w=2
cheers.
--
Nathan
|