All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jogi Hofmüller" <jogi@mur.at>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: rootfs crash
Date: Wed, 18 Sep 2013 20:15:31 +0200	[thread overview]
Message-ID: <5239EDC3.2060804@mur.at> (raw)
In-Reply-To: <CAFvQSYS7U6VdYeUa-BocBq2tgQuyg1Z_eqpO=6UkcER2a1_p-g@mail.gmail.com>

Hi Clemens, all,
Am 2013-09-17 20:53, schrieb Clemens Eisserer:

> a. comment out the free()-calls which led to crashes

Uh, well, I did not want to go that far ;)  I'm certainly not the
greatest programmer around, but not freeing allocated memory seems kind
of drastic.

Anyway, I checked out a copy of btrfs-progs from git and took a look at
the code.  Then I remembered valgrind and instead of running btrfs
restore on the broken machine I tried it on my images (saved with dd on
an external hard drive).  Running the self-compiled program using sudo
resulted in the same errors.

Now the (at least for me) fun part.  Running it under my UID I managed
to retrieve 13GB worth of data so far before hitting the same error:

  Error in `./btrfs': free(): invalid next size (normal)

I would be glad for someone's opinion on this.

Regards!
-- 
j.hofmüller

  reply	other threads:[~2013-09-18 18:15 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 [this message]
2013-09-19 16:18             ` Frank Holton
2013-09-19 17:07               ` Jogi Hofmüller
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=5239EDC3.2060804@mur.at \
    --to=jogi@mur.at \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linuxhippy@gmail.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.