[Top] [All Lists]


To: xfs@xxxxxxxxxxx
Subject: xfs_repair
From: Roman Hlynovskiy <roman.hlynovskiy@xxxxxxxxx>
Date: Thu, 14 Nov 2013 23:51:47 +0600
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DoS0dLcyA8O49jhSufRy4GAKdiSp4K6L3xFWHVcVCHI=; b=WoPNnQOITfKGUTYI4Dgj/QFI5IyTpH1Narf5YYOTXlocBJlIc29AsuAReTzIN9zHaM eL83fc2skYAtbHTaTwAI0OGl7njVhNoa2H1O9kvSnbD9RVhD/W7k+r7aiwnxB+elVx5W dSTybTMuWpvD6vdwWxHD+MDgJoU4wanlG/+4wl0aG4xpLLxB2TjL76WgrlzUOfsvKFKX 35vsskkUGKh/3CgilcIdmwA7iA3CNbzMJB33Q4x1yuFSOlpOHfhphcS1t37iGucL/Vv4 +ILPMil6HKyDMcvN9wQlN+IvinYD3XEB+PQVXLDkfgzuSB+yhl4l35vtvHiG6Nedy/h0 ktXQ==
hello, after a server crush we are trying to get back access to data on another server.

out setup is the following:
4 disks in md-array, lvm over it and xfs

xfs_check just stops with 'out of memory error'
xfs_repair after a long list of complains says:

corrupt dinode 2473604576, extent total = 1, nblocks = 0.  This is a bug.
Please capture the filesystem metadata with xfs_metadump and
report it to xfs@xxxxxxxxxxx.
cache_node_purge: refcount was 1, not zero (node=0xb43ab688)

fatal error -- 117 - couldn't iget disconnected inode

I captured this metadata file, but it's 2GB size.
is there a chance to fix the fs?

...WBR, Roman Hlynovskiy
<Prev in Thread] Current Thread [Next in Thread>