xfs
[Top] [All Lists]

Re: how cant I rebuild the superblock

To: linux-xfs@xxxxxxxxxxx
Subject: Re: how cant I rebuild the superblock
From: Sven Gehr <sven@xxxxxxxxxxxxx>
Date: Wed, 30 Mar 2005 23:02:32 +0200 (CEST)
In-reply-to: <20050330205513.GA13965@taniwha.stupidest.org>
Organization: dreampixel
References: <424ACFBC.3010304@xfs.org> <30102190.1112199967909.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330174259.GB11762@taniwha.stupidest.org> <5896993.1112208569856.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330185324.GA12530@taniwha.stupidest.org> <22377952.1112209168690.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330190118.GA12758@taniwha.stupidest.org> <12241337.1112210187657.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330192000.GA13002@taniwha.stupidest.org> <120224.1112215280479.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330205513.GA13965@taniwha.stupidest.org>
Reply-to: sven@xxxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
Am Mi 30.03.2005 22:55 schrieb Chris Wedgwood <cw@xxxxxxxx>:
> On Wed, Mar 30, 2005 at 10:41:20PM +0200, Sven Gehr wrote:

 
> > corrupt inode 134762498 (btree). Umount and run xfs_repair.  fatal
> > error -- 990 - couldn' iget disconnected inode
 
> xfs_repair says that?  what is the full ouput?

the complete? bevor the break:

[...]
disconnected indode 134746172, moving to lost+found
disconnected indode 134746173, moving to lost+found
disconnected indode 134746174, moving to lost+found
disconnected indode 134746175, moving to lost+found

Whe you need more output I can it log in a file and send?


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