All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: linux-btrfs@vger.kernel.org
Subject: segmentation-fault in btrfsck (git-version)
Date: Wed, 05 Dec 2012 21:50:58 +0100	[thread overview]
Message-ID: <50BFB3B2.8040405@friedels.name> (raw)

Dear all,

thanks for developing btrfsck!
Now, I'd like to contribute -as far as I can. I'm not a developer, but I 
do have some linux-experience.
I've been using btrfsck on two 3TB HDDs (mirrored) for a while now under 
Kernel 3.0. Now it's corrupt. I had some hard resets of the machine 
-which might have contributed. I do have a backup of the data -at least 
of the important stuff. Some TV-Recordings are missing. The reason I am 
writing is, to support the development.

Unfortunately, btrfsck (latest git-version) crashes with a segmentation 
fault, when trying to repair this.

Here's the backtrace:
root 261 inode 64375 errors 400
root 261 inode 64376 errors 400
btrfsck: disk-io.c:382: __commit_transaction: Assertion `!(!eb || 
eb->start != start)' failed.

Program received signal SIGABRT, Aborted.
0x00007ffff784c425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
(gdb) backtrace
#0  0x00007ffff784c425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff784fb8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ffff78450ee in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007ffff7845192 in __assert_fail () from 
/lib/x86_64-linux-gnu/libc.so.6
#4  0x000000000040d3ae in __commit_transaction (trans=0x62e010, 
root=0xb66ae0) at disk-io.c:382
#5  0x000000000040d4d8 in btrfs_commit_transaction (trans=0x62e010, 
root=0xb66ae0) at disk-io.c:415
#6  0x000000000040743d in main (ac=<optimized out>, av=<optimized out>) 
at btrfsck.c:3587


Now, here's where my debugging knowledge ends. Are you interested in 
debugging this further, or is it a known bug?

Regards,
Hendrik
-- 
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363

             reply	other threads:[~2012-12-05 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 20:50 Hendrik Friedel [this message]
2012-12-06 19:09 ` segmentation-fault in btrfsck (git-version) Mitch Harder
2012-12-08 13:04   ` Hendrik Friedel
2012-12-09 19:06   ` Hendrik Friedel
2012-12-09 20:42     ` Mitch Harder
2012-12-15 19:40       ` Hendrik Friedel
2012-12-15 22:24         ` Mitch Harder
2012-12-18 22:17           ` Hendrik Friedel
2012-12-29 11:28             ` Hendrik Friedel
2012-12-30 19:34               ` Mitch Harder

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=50BFB3B2.8040405@friedels.name \
    --to=hendrik@friedels.name \
    --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.