Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Scotty Edmonds <scotty@scottyedmonds.com>,
	Austin S Hemmelgarn <ahferroin7@gmail.com>,
	Hugo Mills <hugo@carfax.org.uk>,
	Donald Pearson <donaldwhpearson@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS Error - Rockstor
Date: Thu, 19 Nov 2015 14:14:24 +0800	[thread overview]
Message-ID: <564D68C0.8010300@cn.fujitsu.com> (raw)
In-Reply-To: <SN2PR07MB013DC7E3D1F0FB1D5ED906ECF1C0@SN2PR07MB013.namprd07.prod.outlook.com>



Scotty Edmonds wrote on 2015/11/18 12:50 +0000:
> (gdb) run rescue chunk-recover -y /dev/sdg
> Starting program: /usr/sbin/btrfs rescue chunk-recover -y /dev/sdg
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Thread 0x7ffff6f85700 (LWP 4140)]
> [New Thread 0x7ffff6784700 (LWP 4141)]
> [New Thread 0x7ffff5f83700 (LWP 4142)]
> [New Thread 0x7ffff5782700 (LWP 4143)]
> [New Thread 0x7ffff4f81700 (LWP 4144)]
> Scanning: 2441862246400 in dev0, 2068329484288 in dev1, 3000574365696 in dev2, 2233151475712 in dev3, 2449691725824 in dev4[Thread 0x7ffff5f83700 (LWP 4142) exited]
> Scanning: 2999962390528 in dev0, 2566459445248 in dev1, DONE in dev2, 2748207828992 in dev3, 3000592969728 in dev4[Thread 0x7ffff4f81700 (LWP 4144) exited]
> Scanning: 3000580788224 in dev0, 2567040225280 in dev1, DONE in dev2, 2748795932672 in dev3, DONE in dev4[Thread 0x7ffff6f85700 (LWP 4140) exited]
> Scanning: DONE in dev0, 2806774272000 in dev1, DONE in dev2, 3000592969728 in dev3, DONE in dev4[Thread 0x7ffff5782700 (LWP 4143) exited]
> Scanning: DONE in dev0, 3000592969728 in dev1, DONE in dev2, DONE in dev3, DONE in dev4[Thread 0x7ffff6784700 (LWP 4141) exited]
> Scanning: DONE in dev0, DONE in dev1, DONE in dev2, DONE in dev3, DONE in dev4
>
> Program received signal SIGFPE, Arithmetic exception.
> 0x00000000004273d8 in calc_stripe_length ()
> (gdb)

Good enough to fix the float point error.
The patch will come soon.

Thanks for the info and help from Austin.
Qu
>
> (gdb) bt
> #0  0x00000000004273d8 in calc_stripe_length ()
> #1  0x000000000043191e in btrfs_recover_chunk_tree ()
> #2  0x000000000042f473 in cmd_rescue_chunk_recover ()
> #3  0x000000000040ea72 in main ()
> (gdb)
>
> Thanks,
>
> Scotty Edmonds
> Scotty@ScottyEdmonds.com
>
> ________________________________________
> From: Austin S Hemmelgarn <ahferroin7@gmail.com>
> Sent: November-17-15 8:38 AM
> To: Scotty Edmonds; Qu Wenruo; Hugo Mills; Donald Pearson
> Cc: Btrfs BTRFS
> Subject: Re: BTRFS Error - Rockstor
>
> On 2015-11-17 03:08, Scotty Edmonds wrote:
>> Sorry, I'm not at all familiar with backtrace.
>>
> General procedure to get a backtrace on a system without core files:
> 1. Make sure you have debugging symbols installed for the program you
> want the backtrace for, and ideally any libraries it uses.  (These
> usually are in packages with names ending in -dbg or -debug.  In the
> case of btrfs, you'll probably need symbols for glibc, lzo, and zlib).
> 2. Start the program under gdb ('gdb /sbin/btrfs')
> 3. When gdb is done loading, type in 'start' followed by the arguments
> for the program (in this case, 'rescue chunk-recover -y /dev/sdg')
> 4. If gdb then says something about stopping at a breakpoint, enter the
> command 'continue'.
> 5. When the program being debugged crashes, you should get a backtrace
> from gdb, if not, you can enter the command 'bt' to tell it to dump a
> backtrace.
> 6. After copying the backtrace somewhere you can put it in an e-mail,
> you can exit gdb with the 'exit' command, it may complain about
> something still running, it's safe to tell it to kill this process.
>
> If instead you have your system configured for core dumps:
> 1. Make sure you have debugging symbols installed for the program you
> want the backtrace for, and ideally any libraries it uses.
> 2. Run gdb with the program and core file ('gdb /sbin/btrfs
> /path/to/core/file').
> 3. Enter the command 'bt to get a backtrace.
>

      reply	other threads:[~2015-11-19  6:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 18:48 BTRFS Error - Rockstor Scotty Edmonds
2015-11-12 18:55 ` Donald Pearson
     [not found]   ` <SN2PR07MB013F045DB3B42E4AD8AA3D6CF120@SN2PR07MB013.namprd07.prod.outlook.com>
2015-11-12 22:19     ` Donald Pearson
     [not found]       ` <SN2PR07MB01362A586F4293204E66FCFCF120@SN2PR07MB013.namprd07.prod.outlook.com>
2015-11-12 22:41         ` Donald Pearson
2015-11-12 22:57           ` Hugo Mills
2015-11-13  1:46             ` Scotty Edmonds
2015-11-13  2:21               ` Qu Wenruo
2015-11-13  2:21               ` Qu Wenruo
2015-11-13  2:23                 ` Scotty Edmonds
2015-11-13  3:00                   ` Qu Wenruo
2015-11-13  3:05                     ` Scotty Edmonds
2015-11-13  3:25                       ` Qu Wenruo
2015-11-16  1:06                   ` Qu Wenruo
2015-11-17  7:09                     ` Scotty Edmonds
2015-11-17  7:35                       ` Qu Wenruo
2015-11-17  8:08                         ` Scotty Edmonds
2015-11-17 12:38                           ` Austin S Hemmelgarn
2015-11-18 12:50                             ` Scotty Edmonds
2015-11-19  6:14                               ` Qu Wenruo [this message]

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=564D68C0.8010300@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=ahferroin7@gmail.com \
    --cc=donaldwhpearson@gmail.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=scotty@scottyedmonds.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox