From: Su Yue <suy.fnst@cn.fujitsu.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, <linux-btrfs@vger.kernel.org>,
Su Yue <Damenly_Su@gmx.com>
Subject: Re: btrfs check lowmem, take 2
Date: Wed, 11 Jul 2018 09:58:36 +0800 [thread overview]
Message-ID: <9b0990aa-05aa-3e0e-463f-b4eb9894dc81@cn.fujitsu.com> (raw)
In-Reply-To: <20180711014401.hic5vcp5h2tzgyxh@merlins.org>
On 07/11/2018 09:44 AM, Marc MERLIN wrote:
> On Wed, Jul 11, 2018 at 09:08:40AM +0800, Su Yue wrote:
>>
>>
>> On 07/11/2018 08:58 AM, Marc MERLIN wrote:
>>> On Wed, Jul 11, 2018 at 08:53:58AM +0800, Su Yue wrote:
>>>>> Problems
>>>>> 1) btrfs check --repair _still_ takes all 32GB of RAM and crashes the
>>>>> server, despite my deleting lots of snapshots.
>>>>> Is it because I have too many files then?
>>>>>
>>>> Yes. Original check first gather all infomation about extent tree and
>>>> your files in RAM, then process one by one.
>>>> But deleting still counts, it does speed lowmem check up.
>>>
>>> Understood.
>>>
>>>>> 2) I tried Su's master git branch for btrfs-progs to try and see how
>>>> Oh..No... My master branch is still 4.14. The true mater branch is
>>>> David's here:
>>>> https://github.com/kdave/btrfs-progs
>>>> But the master branch has a known bug which I fixed yesterday, please see
>>>> the mail.
>>>
>>> So, if I git sync it now, it should have your fix, and I can run it,
>>> correct?
>>>
>> Yes, please.
>
> Ok, I am now running
> gargamel:~# time btrfs check --mode=lowmem --repair /dev/mapper/dshelf2
> using git master from https://github.com/kdave/btrfs-progs
>
Please stop check, plese.
The branch 'it' which I mean is
https://github.com/Damenly/btrfs-progs/tree/tmp1
> I will report back how long it takes with extent tree check and whether
> it returns clean, or not.
>
> Marc
>
next prev parent reply other threads:[~2018-07-11 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 18:09 btrfs check lowmem, take 2 Marc MERLIN
2018-07-11 0:53 ` Su Yue
2018-07-11 0:58 ` Marc MERLIN
2018-07-11 1:08 ` Su Yue
2018-07-11 1:44 ` Marc MERLIN
2018-07-11 1:58 ` Su Yue [this message]
2018-07-11 3:36 ` Marc MERLIN
2018-07-11 4:07 ` Su Yue
2018-07-11 4:39 ` Marc MERLIN
2018-07-11 17:09 ` Chris Murphy
2018-07-11 17:14 ` btrfs check mode normal still hard crash-hanging systems Marc MERLIN
2018-07-12 5:26 ` Why original mode doesn't use swap? (Original: Re: btrfs check lowmem, take 2) Qu Wenruo
2018-07-12 23:14 ` Marc MERLIN
2018-07-13 0:22 ` 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=9b0990aa-05aa-3e0e-463f-b4eb9894dc81@cn.fujitsu.com \
--to=suy.fnst@cn.fujitsu.com \
--cc=Damenly_Su@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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 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.