From: Sean Bartell <wingedtachikoma@gmail.com>
To: Alli Quaknaa <alquaknaa@gmail.com>
Cc: Wengang Wang <wen.gang.wang@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: Restoring BTRFS partition
Date: Tue, 20 Apr 2010 20:32:15 -0400 [thread overview]
Message-ID: <20100421003045.GA10361@flcl.lan> (raw)
In-Reply-To: <q2u8c113a261004201525kebe2462agaca1d5fb81773cef@mail.gmail.com>
On Tue, Apr 20, 2010 at 10:25:34PM +0000, Alli Quaknaa wrote:
> I think I have found the real superblock you are talking about, but
> I'm afraid I may have written something in the first 64MiB. Is there a
> chance btrfsck will recover it?
btrfsck is currently very limited; it only detects a limited number of
problems, and it can't fix anything. Btrfs focuses on handling problems
when they are discovered while using the FS; generally, it should handle
corruption relatively gracefully. However, if anything really crucial
was overwritten and the FS can't be mounted, there aren't any tools to
repair it.
> Also, I think there's gotta be a better way to manipulate those huge
> files then dd and hexedit for examination - I'd like to take the raw
> file, open it in some hex editor and be able to cut of some of it's
> beginning - I can't seem to be able to do it with hexedit. Is there a
> tool you'd recomment?
For viewing, you can use less, head, and tail with hexdump:
tail -c +$((0x10000+1)) /dev/sda1|hexdump -C|less
will view the disk starting at the superblock. For editing, dd is
probably best, though you could use a hex editor like Okteta. I've also
heard of Radare, supposedly a very advanced command-line tool. Keep in
mind that any tool that deletes the first part of a huge file will be
forced to rewrite the entire file.
next prev parent reply other threads:[~2010-04-21 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 14:56 Restoring BTRFS partition Alli Quaknaa
2010-04-20 15:55 ` Wengang Wang
2010-04-20 16:50 ` Sean Bartell
2010-04-20 17:14 ` Alli Quaknaa
2010-04-20 18:13 ` Alli Quaknaa
2010-04-20 20:30 ` Sean Bartell
2010-04-20 22:25 ` Alli Quaknaa
2010-04-21 0:32 ` Sean Bartell [this message]
2010-04-21 7:45 ` Alli Quaknaa
2010-04-21 2:49 ` Wengang Wang
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=20100421003045.GA10361@flcl.lan \
--to=wingedtachikoma@gmail.com \
--cc=alquaknaa@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wen.gang.wang@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.