All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Groth <christoph@grothesque.org>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Unocorrectable errors with RAID1
Date: Tue, 17 Jan 2017 21:25:28 +0100	[thread overview]
Message-ID: <87lgu9cu2v.fsf@grothesque.org> (raw)
In-Reply-To: <6f5ba97f-0c13-4ad1-fda3-a10db7024ef7@suse.de> (Goldwyn Rodrigues's message of "Tue, 17 Jan 2017 05:32:44 -0600")

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

Goldwyn Rodrigues wrote:
> On 01/17/2017 02:44 AM, Christoph Groth wrote:
>> Goldwyn Rodrigues wrote:
>> 
>>> Would you be able to upload a btrfs-image for me to 
>>> examine. This is a
>>> core ctree error where most probably item size is incorrectly 
>>> registered.
>> 
>> Sure, I can do that.  I'd like to use the -s option, will this 
>> be fine? 
>
> Yes, I think that should be fine.

Unfortunately, giving -s causes btrfs-image to segfault.  I tried 
both btrfs-progs 4.7.3 and 4.4.  I also tried different 
compression levels.

Without -s it works, but since this file system contains the 
complete digital life of our family, I would rather not share even 
the file names.

Any ideas on what could be done?  If you need help to debug the 
problem with btrfs-image, please tell me what I should do.  I can 
keep the broken file system around until an image can be created 
at some later time.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-01-17 20:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 11:10 Unocorrectable errors with RAID1 Christoph Groth
2017-01-16 13:24 ` Austin S. Hemmelgarn
2017-01-16 15:42   ` Christoph Groth
2017-01-16 16:29     ` Austin S. Hemmelgarn
2017-01-17  4:50       ` Janos Toth F.
2017-01-17 12:25         ` Austin S. Hemmelgarn
2017-01-17  9:18       ` Christoph Groth
2017-01-17 12:32         ` Austin S. Hemmelgarn
2017-01-16 22:45 ` Goldwyn Rodrigues
2017-01-17  8:44   ` Christoph Groth
2017-01-17 11:32     ` Goldwyn Rodrigues
2017-01-17 20:25       ` Christoph Groth [this message]
2017-01-17 21:52         ` Chris Murphy
2017-01-17 23:10           ` Christoph Groth
2017-01-18  7:13             ` gdb log of crashed "btrfs-image -s" Christoph Groth
2017-01-18 11:49               ` Goldwyn Rodrigues
2017-01-18 20:11                 ` Christoph Groth
2017-01-23 12:09                   ` Goldwyn Rodrigues
2017-01-17 22:57         ` Unocorrectable errors with RAID1 Goldwyn Rodrigues
2017-01-17 23:22           ` Christoph Groth

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=87lgu9cu2v.fsf@grothesque.org \
    --to=christoph@grothesque.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rgoldwyn@suse.de \
    /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.