From: Dave Chinner <david@fromorbit.com>
To: Alessio Di Maria <alessio.dimaria@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Repair XFS from 1/3 of the table
Date: Tue, 23 Sep 2014 07:05:49 +1000 [thread overview]
Message-ID: <20140922210548.GO4267@dastard> (raw)
In-Reply-To: <CAJiJ=8+1P1odzJGpWRvPQh84KQMx5ukzFS9pACjRr7aHGiTpXQ@mail.gmail.com>
On Fri, Sep 19, 2014 at 10:58:49PM +0200, Alessio Di Maria wrote:
> Hi, for fist i'm sorry for my bad English..
> so,
> I'm trying to do a recovery from my NAS,
> After it stopped, 3 disk of 4 was reinitialized so, raid partition was
> deleted on disk 1 2 and 3, and first about 5m was zero filled..
So you lost the root inode and a lot of other critical metadata.
> I'm actually work on a copy of that...
> in my luck, the XFS superblock was on 4th disk..
> I was able to rebuild RAID5 with the original configuration and now i can
> read RAW files up to few kb... i was able to read a 15Mb zip file, and some
> big jpeg, so i can say that RAID it's working fine
>
> At sector 384 of the raid volume start the xfs superblock, i made a
> loopback at this offset,
> mounting it.. but obviusly it said that was not clean.
> making xfs_repair i get anything, but with xfs_repair -L i had infinite
> list of lost inode, and than i was able to mount the partition,
> but with any file, only the lost + found directory with few but complete
> files...
That happens when you lose the root inode.
> On the NAS there were Big Files of ISCSI, in the lost + found i find one of
> this, big 100Gb.. now i don't know how i can recovery the rest..
If you had regions of of the drives zeroed, then you've lost data
randomly in the files in the filesystem. It's basically
unrecoverable if you don't have a backup.
> Is it possible to find lost inode?
You can google for xfs_irecover, but you've already run xfs_repair
and so it's going to be mostly useless at this point.
> i tryied with many programs to get back the original Filesystem but
> anything up the Lost + Found directory after the repair...
> I know that XFS is based on sparse file, and so i can't find my file and
> hope to copy it contigusly (about 5Gb) cose the fs reidirect zero filled
> zone... in addiction i can't do a RAW recovery cose in the deep of 2.7Tb i
> find MFT entryies and system files inner ISCSI units...
> So what chache?
> Wha can i do myself?
If xfs_repair hasn't recovered the inodes that contained the files
you care about, then it's almost certain that you've lost
those files forever unless you have a backup. You can try grepping
the raw device for sectors that contain signatures you care about,
but that only works for contiguous files that were lost (that's
effectively what photorec does).
Other than that, there's nothing that can be done to recover what
has been lost from the corpse you have on your hands...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-09-22 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 20:58 Repair XFS from 1/3 of the table Alessio Di Maria
2014-09-22 21:05 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140922210548.GO4267@dastard \
--to=david@fromorbit.com \
--cc=alessio.dimaria@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox