Running xfs_metadump.sh will give me output below. Does all this mean
it's best to think about alternatives to fixing/recovering these
-g /dev/evms/monster_evms monster.dump
Copied 320 of 112448 inodes (0 of 0 AGs) xfs_db:
metadump.c:465: generate_obfuscated_name: Assertion
`libxfs_da_hashname(newname, namelen) == hash' failed.
./xfs_metadump.sh: line 31: 17542 Aborted
xfs_db$DBOPTS -i -p xfs_metadump -c "metadump$OPTS $2" $1
On Mon, Jun 16, 2008 at 12:47 AM, Barry Naujok <bnaujok@xxxxxxx> wrote:
> On Sun, 15 Jun 2008 02:43:12 +1000, Simon <simonjj@xxxxxxxxx> wrote:
>> Hello all,
>> I have a corrupted xfs filesystem on top of a RAID 5 (1TB in size).
>> The RAID is still fully intact but the filesystem was damaged. When
>> trying to repair the filesystem xfs_repair fails. I have tried various
>> versions of xfs_repair, the latest stable (2.9.8) and the latest trunk
>> (from CVS). I'd love to investigate and/or fix the issue further but I
>> am a bit confused about some of my xfs_repair runs (both done with
>> Could someone shed some light on where the problem could be, I'd be
>> happy to continue digging if I would only know where roughly
> Are you able to generate an xfs_metadump? If you can make that available,
> I should be able to find out the problem pretty easily.