public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Alexey Salmin <alexey.salmin@gmail.com>,
	Jesper Jensen <linux-ext4_mailinglist@elector.dk>,
	linux-ext4@vger.kernel.org
Subject: Re: Formatted/repartitioned wrong disk, arrgh!
Date: Fri, 06 Nov 2009 08:39:33 -0600	[thread overview]
Message-ID: <4AF43525.1040205@redhat.com> (raw)
In-Reply-To: <20091106140415.GA26342@mit.edu>

Theodore Tso wrote:
> On Fri, Nov 06, 2009 at 05:57:14PM +0600, Alexey Salmin wrote:
>> I think the only thing I can recommend to you is to "grep for your
>> files and hope for the best" (c)
>> I don't know any automated way to restore files after complete
>> destroying of fs, but there always is grep and hexdump :)
> 
> Unfortunately, there isn't much else that can be done, since the inode
> table has been zero'ed out.
> 
> Sorry.  :-(
> 
> 						- Ted

Well, if you repartitioned / moved the partition, then the new mkfs 
likely wouldn't have perfectly overwritten the old metadata structures, 
so if you can re-partition again and put the starting sector -back- at 
the original location, an e2fsck might have a fighting chance to find 
-something- ...

-Eric

  reply	other threads:[~2009-11-06 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 10:19 Formatted/repartitioned wrong disk, arrgh! Jesper Jensen
2009-11-06 10:49 ` Alexey Salmin
2009-11-06 11:49   ` Jesper Jensen
2009-11-06 11:57     ` Alexey Salmin
2009-11-06 14:04       ` Theodore Tso
2009-11-06 14:39         ` Eric Sandeen [this message]
2009-11-06 16:01           ` Theodore Tso
2009-11-06 14:43         ` Alexey Fisher
2009-11-06 15:02           ` Greg Freemyer
2009-11-06 16:06             ` Jesper Jensen

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=4AF43525.1040205@redhat.com \
    --to=sandeen@redhat.com \
    --cc=alexey.salmin@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-ext4_mailinglist@elector.dk \
    --cc=tytso@mit.edu \
    /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