From: "Jogi Hofmüller" <jogi@mur.at>
To: linux-btrfs@vger.kernel.org
Cc: Frank Holton <fholton@gmail.com>
Subject: Re: rootfs crash
Date: Thu, 19 Sep 2013 19:07:23 +0200 [thread overview]
Message-ID: <523B2F4B.6050702@mur.at> (raw)
In-Reply-To: <CAC4gV=57gOWABD3n+fhEkxRVDKKeejKSQYVEC-M=V2rDXr8Uog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Hello Frank,
Am 2013-09-19 18:18, schrieb Frank Holton:
> I'm not sure what's causing the free error, I'll keep looking.
So am I :) In fact I would really like to help fix the tool. I hope I
can provide some suggestions for fixes, but I'm having my trouble with
the code ;)
All I can tell so far is that when you run `btrfs restore` via valgrind
you get much farther then without. But even that eventually crashes :(
> Have you tried running restore on your home subvolume yet? By default
> restore only works on the default subvolume which in your case is /
I managed to retrieve almost everything from /home/. I am even working
on the machine that had the crashed file system now :)
> The following command will try to restore your /home subvolume
> btrfs restore -i -r 258 [image] [destination]
Good point! I could not find any references to restoring only parts of
the file system. It's just a pain to see it restoring everything in
/var/cache/apt/archives ... and stopping before it get's to `valuable`
data ;)
> Run that and see if you get your home folder restored. Hopefully the
> errors are only on the root volume.
I will give it another try since I have backups of the corrupted devices
anyhow and will use them as test ground now.
Thanks for your reply!
Cheers!
--
j.hofmüller
Optimism doesn't alter the laws of physics. - Subcommander T'Pol
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2013-09-19 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 10:48 rootfs crash Jogi Hofmüller
2013-09-17 10:51 ` Jogi Hofmüller
2013-09-17 11:18 ` Sander
2013-09-17 12:24 ` Jogi Hofmüller
2013-09-17 15:23 ` Jogi Hofmüller
2013-09-17 18:53 ` Clemens Eisserer
2013-09-18 18:15 ` Jogi Hofmüller
2013-09-19 16:18 ` Frank Holton
2013-09-19 17:07 ` Jogi Hofmüller [this message]
2013-09-20 4:49 ` Jérôme Poulin
2013-09-20 7:58 ` Jogi Hofmüller
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=523B2F4B.6050702@mur.at \
--to=jogi@mur.at \
--cc=fholton@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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.