|Subject:||cannot repair XFS partition|
|From:||"Gergely Soos" <soger@xxxxxxxxxxxxxxxxxxxxx>|
|Date:||Tue, 6 Jan 2009 04:28:15 +0200|
|Dkim-signature:||v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=reYfbd1PxnDQpekYawIaG1m0q938iIg1f3rJzc0pBtI=; b=rpT5apd/c0JMJOyPpXWb1/c0SmRrVqOWvIywe5UjjVpzoV6FhapxxmAl21gl2osEeF 5BMgDZOu8rzQi52mc+LMEJaUZWP1LNp/dqlOKxs4mf0uMuBN4bGi+i+qVpVranhtEQNg BbF6e75vz15XZGxdeqFwNcC4ZjFcTDrrQiUeQ=|
|Domainkey-signature:||a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=fbrDWQoLEb8q0gZgnWQGLG8aib82LBRTqBPXxgTlG9be6a731Lee6LAD6OenpuN7Lb u0PAGBsSnCgnHmfhgiH3qPn3THUcsHB1GKh1NjFCKqmqa1cBPAcIl3dyjBBZPRhuW5Io I3pc/Zl8x2JA2gQE+w1XFRa8aDK25XBYup+gc=|
I heard that people compliment XFS for being the fastest FS these days so I thought I give it a try.
What I did was that I converted my old 107GB FAT32 partition to XFS (I created an XFS over it) and I wanted to use it as /home
Everything went as it should, I moved the files from my old /home then I restarted (cleanly!) under windows.
When I got back from windows I was no longer able to mount the XFS partition.
xfs_repair only said that the superblock is invalid and attempts to find secondary superblocks but all candidates fail.
So I created a file on another computer with the exact same size as the partition on my computer and created an XFS on it.
Then I extracted the first 512 bytes and copied to my HDD using dd. But it complained about the UUID so I corrected it using khexedit.
Then xfs_db complained that it cannot find the root inode so I wrote a little perl script to search it.
You can find it in myxfs.tar.bz2. It seems that it found the root inode because after I corrected the address using khexedit
xfs_db started complaining about the realtime bitmap inodes, so I corrected those too (using inode numbers rootino+1 and rootino+2).
And this is where I'm stuck.
The mount still fails, dmesg says that it cannot find the root inode, xfs_repair says the same old thing, xfs_check says a lot of things,
most of them are messages like this: can't seek in filesystem at bb <some numbers> or: ag bad magick number.
That exceeds my knowledge.
Please help me restore the partition, It contains lots of programmes I wrote over the years and some of them are not backed up,
some of them are, but only an older version. I also have personal stuff on it like my bill records that I cannot recover from anywhere else.
myxfs.tar.bz2 contains the perl script I mentioned above and the inodes it found. The one staring with ri is the root inode,
the files starting with sb are the suspected superblocks (I also took one of those at random and corrected the three inode numbers
with khexedit but the result is the same) and the file backup_bootsect contains the original superblock that was on the disk after I came back
from windows xp. It does not look like anything to me...
The numbers after ri and sb are the starting address in bytes of the inode on the disk.
I've also attached the output of xfs_metadump. This was created after I corrected the three inode numbers in the superblock.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [patch] mm: fix lockless pagecache reordering bug (was Re: BUG: soft lockup - is this XFS problem?), Paul E. McKenney|
|Next by Date:||Re: [patch] mm: fix lockless pagecache reordering bug (was Re: BUG: soft lockup - is this XFS problem?), Linus Torvalds|
|Previous by Thread:||your site, Rick Garrison|
|Next by Thread:||need help to repair XFS partition, Gergely Soos|
|Indexes:||[Date] [Thread] [Top] [All Lists]|