xfs
[Top] [All Lists]

Re: data recovery after hdd failure

To: linux-xfs@xxxxxxxxxxx
Subject: Re: data recovery after hdd failure
From: thomas <tom@xxxxxxx>
Date: Sun, 21 Jul 2002 16:27:09 +0200
In-reply-to: <4.3.2.7.2.20020721103502.03ceb2b0@xxxxxxxxxxxxx>
References: <4.3.2.7.2.20020721103502.03ceb2b0@xxxxxxxxxxxxx>
Reply-to: thomas <tom@xxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
here is some update:

i dd'ed hdc2 (the xfs partition, that was hdc5 originally) to /dev/hda5
and luckily there were only a few bad blocks. so i began the recovery
process, with no luck so far, maybe some can put some insight into this
output, it would be much appreciated.

+:~# xfs_check /dev/hda5
bad magic # 0x1dae3fd0 in inode 280 bmbt block 1/618521
expected level 0 got 25074 in inode 280 bmbt block 1/618521
bad btree nrecs (33556, min=127, max=254) in inode 280 bmap block 1667097
extent count for ino 280 data fork too low (0) for file format
bad nblocks 192516 for inode 280, counted 1
bad nextents 10 for inode 280, counted 0
bad directory data magic # 0xc7beef5c for dir ino 1376607 block 0
no . entry for directory 1376607
no .. entry for directory 1376607
...
...
bad sb magic # 0 in ag 1
bad sb version # 0 in ag 1
bad agf magic # 0 in ag 1
bad agf version # 0 in ag 1
bad agi magic # 0 in ag 1
bad agi version # 0 in ag 1
...
...
bad sb magic # 0x68 in ag 9
bad sb version # 0xffff in ag 9
bad agf magic # 0x68 in ag 9
bad agf version # 0 in ag 9
bad agi magic # 0x68 in ag 9
bad agi version # 0x4f0 in ag 9
/usr/sbin/xfs_check: line 62: 11115 Segmentation fault      xfs_db$ISFILE -i -p 
xfs_check -c "check$OPTS" $1

so this thing at least still gets recognized as a xfs partition. however
it segfaults after ~400 lines of output.

+:~# xfs_repair -n /dev/hda5
Phase 1 - find and verify superblock...
couldn't verify primary superblock - not enough secondary superblocks with 
matching geometry !!!
attempting to find secondary superblock........

and this goes on for a while, xfs_repair finds about 15 secondary
superblocks but cant verify any of them. so it exits with no result.

+:~# od -c /dev/hda5 | less
0000000   X   F   S   B  \0  \0 020  \0  \0  \0  \0  \0 001 035   M 263
0000020  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0000040 267 022 226 276 031   )   L   - 263 327   < 367 316 261 345   4
0000060  \0  \0  \0  \0  \0 220  \0 004  \0  \0  \0  \0  \0  \0  \0 200
0000100  \0  \0  \0  \0  \0  \0  \0 201  \0  \0  \0  \0  \0  \0  \0 202
0000120  \0  \0  \0 020  \0 020  \0  \0  \0  \0  \0 022  \0  \0  \0  \0
0000140  \0  \0  \b 352     204 002  \0 001  \0  \0 020  \0  \0  \0  \0
0000160  \0  \0  \0  \0  \0  \0  \0  \0  \f  \t  \b 004 024  \0  \0 031
0000200  \0  \0  \0  \0  \0  \0 200 300  \0  \0  \0  \0  \0  \0   C 335
0000220  \0  \0  \0  \0  \0   5   z   }  \0  \0  \0  \0  \0  \0  \0  \0
0000240  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0000260  \0  \0  \0  \0  \0  \0  \0 002  \0  \0  \0  \0  \0  \0  \0  \0
0000300  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0001000   X   A   G   F  \0  \0  \0 001  \0  \0  \0  \0  \0 020  \0  \0
0001020  \0  \0  \0 001  \0  \0  \0 002  \0  \0  \0  \0  \0  \0  \0 001
0001040  \0  \0  \0 001  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 003
0001060  \0  \0  \0 004  \0 002 036   r  \0 001 006 344  \0  \0  \0  \0
0001100  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0002000   X   A   G   I  \0  \0  \0 001  \0  \0  \0  \0  \0 020  \0  \0
0002020  \0  \0  \a  \0  \0  \0  \0 003  \0  \0  \0 001  \0  \0 004   ~
0002040  \0   $   + 300 377 377 377 377 377 377 377 377 377 377 377 377
0002060 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377

so the geometry seems to be right, the partition starts with the xfs
superblock. why is the recovery not working then? is there sth. i can do
to help xfs_repair? again any input is much appreciated :)

thomas

ps. since i'm not subscribed i really hope this shows up right on the
list.


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