[Top] [All Lists]

Re: how cant I rebuild the superblock

To: Sven Gehr <sven@xxxxxxxxxxxxx>
Subject: Re: how cant I rebuild the superblock
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 1 Apr 2005 11:44:05 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <21360867.1112254529460.OPEN-XCHANGE.WebMail.wwwrun@postgirl>; from sven@dreampixel.de on Thu, Mar 31, 2005 at 09:35:29AM +0200
References: <20050330190118.GA12758@taniwha.stupidest.org> <12241337.1112210187657.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330192000.GA13002@taniwha.stupidest.org> <120224.1112215280479.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <424B124B.3070706@xfs.org> <20000831.1112216715240.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <424B1EDF.6060508@xfs.org> <19480755.1112223834401.OPEN-XCHANGE.WebMail.wwwrun@postgirl> <20050330235545.GD867@frodo> <21360867.1112254529460.OPEN-XCHANGE.WebMail.wwwrun@postgirl>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Thu, Mar 31, 2005 at 09:35:29AM +0200, Sven Gehr wrote:
> Am Do 31.03.2005 01:55 schrieb Nathan Scott <nathans@xxxxxxx>:
> The Partion is 135,6GB. ~20-30GB in use.

Hmm, yes, thats a bit too large.

> > You can dump the inode by pointing xfs_db at the device:
> > # xfs_db -r -c 'inode 134762498' -c 'print' /dev/mdXXX
> core.format = 3 (btree)
> core.size = 74027919512570268
> core.nblocks = 0
> core.dmevmask = 0x38020000
> core.dmstate = 273

These all look pretty wierd... I'd start with reseting all these to
sane default values, then run repair again.  I created a file like
yours, and repair was OK with it, so possibly there'll be some other
issues - send me the repair output if it still fails after resetting.
So, the db commands would be something like:

# xfs_db -x /dev/mdXXX
xfs_db> inode 134762498
xfs_db> write core.format 2
xfs_db> write core.size 0
xfs_db> write core.dmevmask 0
xfs_db> write core.dmstate 0
xfs_db> quit

then run xfs_repair again and see how that goes.



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