public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: hallexh@gmail.com
Cc: xfs@oss.sgi.com
Subject: Re: Overwritten partition
Date: Tue, 2 Jun 2015 06:50:03 +1000	[thread overview]
Message-ID: <20150601205003.GJ24666@dastard> (raw)
In-Reply-To: <556A3E25.6010706@gmail.com>

On Sun, May 31, 2015 at 12:48:05AM +0200, hallexh@gmail.com wrote:
> Hello,
> 
> I accidentally overwritten first 40GB of 36TB XFS partition. I ran
> xfs_repair then, which resets the superblocks (I'm sorry i didn't copied
> the output of it) and after I mounted the partition, there was no files.
> Empty file system, but It should be almost 90% full.

SOunds like a case of using inode32 allocator, and losing the entire
inode btree (i.e. the index that tracks allocated inodes) as well as
the root inode, hence there being no way to easily discover and
reconstruct the directory tree at all.

> Am I really screwed or there's a chance to recover the data
> somehow?

disaster recovery tools are your only real hope at this point. go
searching for xfs_irecover as a good starting point for scraping
inodes out of the corpse and hence hopefully being able to
reconstruct some of the directory structure...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2015-06-01 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30 22:48 Overwritten partition hallexh
2015-06-01 11:13 ` Emmanuel Florac
2015-06-01 18:28   ` Greg Freemyer
2015-06-01 20:50 ` 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=20150601205003.GJ24666@dastard \
    --to=david@fromorbit.com \
    --cc=hallexh@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