All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nik." <btrfs@avgustinov.eu>
To: Chris Murphy <lists@colorremedies.com>
Cc: Jeff Mahoney <jeffm@suse.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: interest in post-mortem examination of a BTRFS system and improving the btrfs-code?
Date: Fri, 12 Apr 2019 12:52:06 +0200	[thread overview]
Message-ID: <9bac5d98-4de7-e49b-58d2-8e81ce90252c@avgustinov.eu> (raw)
In-Reply-To: <CAJCQCtR6Syn3LYCVOciGPLEpP91Jb9tYp=NncnC2aCNv6coyEw@mail.gmail.com>



2019-04-05 09:07, Chris Murphy:
> On Fri, Apr 5, 2019 at 12:45 AM Nik. <btrfs@avgustinov.eu> wrote:
>>
>> Sorry, I forgot this. Hier is the output:
>>
>> # btrfs-image -c 9 -ss /dev/sdj3 /mnt/b/sdj3.img
>> WARNING: cannot find a hash collision for '..', generating garbage, it
>> won't match indexes
>>
>> The new image is same size, and since it seems small to me I am
>> attaching it to this mail.
> 
> What do you get for `btrfs insp dump-t -d /dev/` ?
> 
> Once I restore it, I get
> 
> 
> $ sudo btrfs insp dump-t -d /dev/mapper/vg-nik
> btrfs-progs v4.20.2
> checksum verify failed on 90195087360 found 6036BAAE wanted 7C05A75D
> checksum verify failed on 90195087360 found 6036BAAE wanted 7C05A75D
> bad tree block 90195087360, bytenr mismatch, want=90195087360,
> have=7681037117263365436
> Couldn't setup device tree
> ERROR: unable to open /dev/mapper/vg-nik
> $ sudo btrfs insp dump-t -r /dev/mapper/vg-nik
> btrfs-progs v4.20.2
> checksum verify failed on 90195087360 found 6036BAAE wanted 7C05A75D
> checksum verify failed on 90195087360 found 6036BAAE wanted 7C05A75D
> bad tree block 90195087360, bytenr mismatch, want=90195087360,
> have=7681037117263365436
> Couldn't setup device tree
> ERROR: unable to open /dev/mapper/vg-nik
> $
> 
> There is a valid superblock however. So it restored something, just
> not everything, not sure. Might be related to create failed success!
> 

Do anybody need something else from this filesystem? If not - I would be 
glad to reformat and reuse this ssd partition.

Kind regards,
Nik.
--

  parent reply	other threads:[~2019-04-12 10:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aa81a49a-d5ca-0f1c-fa75-9ed3656cff55@avgustinov.eu>
2019-03-31 18:44 ` interest in post-mortem examination of a BTRFS system and improving the btrfs-code? btrfs
2019-04-02  0:24   ` Qu Wenruo
2019-04-02 13:06     ` Nik.
2019-04-02 13:24       ` Qu Wenruo
2019-04-02 13:29         ` Hugo Mills
2019-04-02 14:05           ` Nik.
2019-04-02 13:59         ` Nik.
2019-04-02 14:12           ` Qu Wenruo
2019-04-02 14:19             ` Hans van Kranenburg
2019-04-02 15:04               ` Nik.
2019-04-02 15:07                 ` Hans van Kranenburg
2019-04-02 21:22             ` Nik.
2019-04-03  1:04               ` Qu Wenruo
2019-04-04 15:27                 ` Nik.
2019-04-05  0:47                   ` Qu Wenruo
2019-04-05  6:58                     ` Nik.
2019-04-05  7:08                       ` Qu Wenruo
     [not found]                         ` <e9720559-eff2-e88b-12b4-81defb8c29c5@avgustinov.eu>
2019-04-05  8:15                           ` Qu Wenruo
2019-04-05 19:38                             ` Nik.
2019-04-06  0:03                               ` Qu Wenruo
2019-04-06  7:16                                 ` Nik.
2019-04-06  7:45                                   ` Qu Wenruo
2019-04-06  8:44                                     ` Nik.
2019-04-06  9:06                                       ` Qu Wenruo
2019-04-06 13:20                                         ` Nik.
2019-04-06 13:22                                           ` Qu Wenruo
2019-04-06 13:28                                             ` Qu Wenruo
2019-04-06 14:19                                             ` Nik.
2019-04-06 23:18                                               ` Qu Wenruo
2019-04-07  7:41                                                 ` Nik.
2019-04-07 18:45                                                   ` Chris Murphy
2019-04-08 13:09                                                     ` Qu Wenruo
2019-04-08 21:22                                                       ` Nik.
2019-04-12 10:44                                                         ` Nik.
2019-04-12 10:50                                                           ` Qu Wenruo
2019-04-12 11:38                                                             ` Nik.
2019-04-12 12:45                                                               ` Qu Wenruo
2019-05-07 17:17                                                             ` Nik.
2019-05-07 17:30                                                               ` Chris Murphy
2019-05-13 12:19                                                                 ` Nik.
2019-04-10 21:03                                                     ` Nik.
2019-04-11  0:45                                                       ` Qu Wenruo
2019-04-02 18:28         ` Chris Murphy
2019-04-02 19:02           ` Hugo Mills
2019-04-04  2:48   ` Jeff Mahoney
2019-04-04 15:58     ` Nik.
2019-04-04 17:31       ` Chris Murphy
     [not found]         ` <beab578a-ccaf-1ec7-c7b6-1ba9cd3743ad@avgustinov.eu>
2019-04-05  7:07           ` Chris Murphy
2019-04-05 12:07             ` Nik.
2019-04-12 10:52             ` Nik. [this message]
2019-04-05  6:53     ` Chris Murphy

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=9bac5d98-4de7-e49b-58d2-8e81ce90252c@avgustinov.eu \
    --to=btrfs@avgustinov.eu \
    --cc=jeffm@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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.