linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nik." <btrfs@avgustinov.eu>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: interest in post-mortem examination of a BTRFS system and improving the btrfs-code?
Date: Fri, 5 Apr 2019 08:58:55 +0200	[thread overview]
Message-ID: <ce8be6b2-1a2f-201f-a4ff-03686b3620f1@avgustinov.eu> (raw)
In-Reply-To: <8fdb5da5-d649-0c0d-1a21-c3f430476afd@gmx.com>



2019-04-05 02:47, Qu Wenruo:
> 
> 
> On 2019/4/4 下午11:27, Nik. wrote:
>>
>>
>> 2019-04-03 03:04, Qu Wenruo:
>>>
>>
>> [snip]
>> ...
>>
>>>>> In your case, you just need latest btrfs-progs and re-run "btrfs check
>>>>> --readonly" on it.
>>>>
>>>> Will try this, but have no time before tomorrow evening.
>>>>
>>>>
>>>>> If it just shows the same result, meaning I can't get the info about
>>>>> which tree block is corrupted, then you could try to mount it with
>>>>> -o ro
>>>>> using *LATEST* kernel.
>>>>
>>>> I tried this before with the 4.15.0-46 kernel, it was impossible. Will
>>>> try again with newer one as soon as possible (in best case tomorrow
>>>> evening); I will post the results.
>>
>> Sorry for the delay, compiling the btrfs-progs took much more time than
>> expected (had to install new packages again and again). Finally had to
>> give up the conversion ("make" could not find reiserfs/misc.h, although
>> both libreiserfscore and reiser4fs are installed).
>> Output of the commands:
>> # uname -r
>> 5.0.6-050006-generic
>> #btrfs --version
>> btrfs-progs v4.20.2
>> # btrfs check --readonly /dev/md0
>> Opening filesystem to check...
>> incorrect offsets 15003 146075
>> ERROR: cannot open file system
>>
>> It seems that I will wait until 5.2 is out...
>> (the answer to Jeff Mahoney is coming with separate e-mail!)
> 
> OK, then you can try mount it with 5.0 with -o ro.

# mount -t btrfs -o ro /dev/md0 /mnt/md0/
mount: /mnt/md0: wrong fs type, bad option, bad superblock on /dev/md0, 
missing codepage or helper program, or other error.

> The objective is not to make it work, but to get the dmesg, which should

# dmesg|tail
[65283.442278] audit: type=1107 audit(1554438151.396:115): pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=kernel msg='Unknown class service 
exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[72504.975359] audit: type=1107 audit(1554445372.928:116): pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=kernel msg='Unknown class service 
exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[72535.214394] audit: type=1107 audit(1554445403.166:117): pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=kernel msg='Unknown class service 
exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[72535.257571] audit: type=1107 audit(1554445403.210:118): pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=kernel msg='Unknown class system 
exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[73427.486853] BTRFS info (device md0): disk space caching is enabled
[73427.938260] BTRFS info (device md0): bdev /dev/md0 errs: wr 0, rd 0, 
flush 0, corrupt 2181, gen 0
[73429.172707] BTRFS critical (device md0): corrupt leaf: root=2 
block=1894009225216 slot=30, unexpected item end, have 146075 expect 15003
[73429.176628] BTRFS critical (device md0): corrupt leaf: root=2 
block=1894009225216 slot=30, unexpected item end, have 146075 expect 15003
[73429.177153] BTRFS error (device md0): failed to read block groups: -5
[73429.197019] BTRFS error (device md0): open_ctree failed


> contain the tree block bytenr, so that we can try to fix that offending
> tree block manually.
> 
> Thanks,
> Qu

Should I try something alse?
Thank you!
Nik.
--
> 
>>
>>>>> Latest kernel will report anything wrong pretty vocally, in that case,
>>>>> dmesg would include the bytenr of corrupted tree block.
>>>>>
>>>>> Then I could craft needed commands to further debug the fs.
>>>>
>>>> Ok, I will try to post more info tomorrow about this time.
>>>>
>>>> Nik.
>>>> -- 
>>>>
>>>>> Thanks,
>>>>> Qu
>>>>>
>>>>>>
>>>>>> Thank you for trying to improve btrfs!
>>>>>>
>>>>>> Nik.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Qu
>>>>>>
>>>>>> You are not from the 007 - lab, are you? ;-)
>>>>>>
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>>
>>>>>>>> Nik.
>>>>>>>
>>>>>
>>>
> 

  reply	other threads:[~2019-04-05  6:59 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. [this message]
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.
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=ce8be6b2-1a2f-201f-a4ff-03686b3620f1@avgustinov.eu \
    --to=btrfs@avgustinov.eu \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).