All of lore.kernel.org
 help / color / mirror / Atom feed
From: Su Yue <suy.fnst@cn.fujitsu.com>
To: Marc MERLIN <marc@merlins.org>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>, <linux-btrfs@vger.kernel.org>
Cc: Su Yue <Damenly_Su@gmx.com>
Subject: Re: btrfs check lowmem, take 2
Date: Wed, 11 Jul 2018 08:53:58 +0800	[thread overview]
Message-ID: <9afce26c-0a3f-3389-ba0f-597b26a8cd7e@cn.fujitsu.com> (raw)
In-Reply-To: <20180710180915.onnxuak7vb7uywyn@merlins.org>



On 07/11/2018 02:09 AM, Marc MERLIN wrote:
> Thanks to Su and Qu, I was able to get my filesystem to a point that
> it's mountable.
> I then deleted loads of snapshots and I'm down to 26.
> 
> IT now looks like this:
> gargamel:~# btrfs fi show /mnt/mnt
> Label: 'dshelf2'  uuid: 0f1a0c9f-4e54-4fa7-8736-fd50818ff73d
> 	Total devices 1 FS bytes used 12.30TiB
> 	devid    1 size 14.55TiB used 13.81TiB path /dev/mapper/dshelf2
> 
> gargamel:~# btrfs fi df /mnt/mnt
> Data, single: total=13.57TiB, used=12.19TiB
> System, DUP: total=32.00MiB, used=1.55MiB
> Metadata, DUP: total=124.50GiB, used=115.62GiB
> Metadata, single: total=216.00MiB, used=0.00B
> GlobalReserve, single: total=512.00MiB, used=0.00B
> 
> 
> 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.

> 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.

Thanks,
Su
> normal check would go, and I'm stuck on this:
> gargamel:/var/local/src/btrfs-progs.sy# time ./btrfsck --mode=lowmem --repair /dev/mapper/dshelf2
> enabling repair mode
> WARNING: low-memory mode repair support is only partial
> Checking filesystem on /dev/mapper/dshelf2
> UUID: 0f1a0c9f-4e54-4fa7-8736-fd50818ff73d
> root 18446744073709551607 has a root item with a more recent gen (143376) compared to the found root node (139061)
> ERROR: failed to repair root items: Invalid argument

Thanks to the failure, the old version didn't do any things wrong.

> 
> real	75m8.046s
> user	0m14.591s
> sys	0m52.431s
> 
> I understand what the message means, I just need to switch to the newer root
> but honestly I'm not quite sure how to do this from the btrfs-check man page.
> 
> This didn't work:
> time ./btrfsck --mode=lowmem --repair --chunk-root=18446744073709551607  /dev/mapper/dshelf2
> enabling repair mode
> WARNING: low-memory mode repair support is only partial
> WARNING: chunk_root_bytenr 18446744073709551607 is unaligned to 4096, ignore it
> 
> How do I address the error above?

> Thanks
> Marc
> 



  reply	other threads:[~2018-07-11  0:49 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 [this message]
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
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=9afce26c-0a3f-3389-ba0f-597b26a8cd7e@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.