All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Scotty Edmonds <scotty@scottyedmonds.com>,
	Qu Wenruo <quwenruo@cn.fujitsu.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: Tue, 17 Nov 2015 07:38:45 -0500	[thread overview]
Message-ID: <564B1FD5.4060101@gmail.com> (raw)
In-Reply-To: <SN2PR07MB0138CA2787C4F7D11B7CECDCF1D0@SN2PR07MB013.namprd07.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]

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.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-11-17 12:39 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 [this message]
2015-11-18 12:50                             ` Scotty Edmonds
2015-11-19  6:14                               ` Qu Wenruo

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=564B1FD5.4060101@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=donaldwhpearson@gmail.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    --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 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.