From: Chris Murphy <chris@colorremedies.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs check lowmem vs original
Date: Fri, 20 Jan 2017 08:10:58 -0700 [thread overview]
Message-ID: <CAJCQCtTdfD6=xWttk5D4JqLpzG9ZMxb-c=GopZPPNsLP6eHHpw@mail.gmail.com> (raw)
In-Reply-To: <6ee63ff7-6a0c-7828-0751-5769d59bb85f@cn.fujitsu.com>
On Thu, Jan 19, 2017 at 10:45 PM, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
>> Another file system, 15 minutes old with two mounts in its whole
>> lifetime, and only written with kernel 4.10-rc3 has over 30 lines of
>> varying numbers:
>>
>> ERROR: root 257 EXTENT DATA[150134 11317248] prealloc shouln't have
>> datasum
>>
>> That file system should have no preallocated extents (It's a clean
>> installation of Fedora Rawhide, using only rsync)
>
>
> btrfs-debug-tree will help to make sure what is wrong.
6b187fa6.logs.tar.gz 20M
https://drive.google.com/open?id=0B_2Asp8DGjJ9SlRvZ2plNXVmTUU
That's the small recent one, generic content. The others are bigger,
and I should probably sanitize the filenames from debug-tree but can't
find in the archives how to do that. Is btrfs-image useful for this?
> That's why lowmem mode is still not the default option.
>
> The problem os original mode is, if you're checking a TB level fs and only 2
> or 4G ram, then it's quite possible you ran out of memory and won't be able
> to check the fs forever, more several than annoying.
Fair enough.
--
Chris Murphy
next prev parent reply other threads:[~2017-01-20 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 4:38 btrfs check lowmem vs original Chris Murphy
2017-01-20 5:45 ` Qu Wenruo
2017-01-20 15:10 ` Chris Murphy [this message]
2017-01-20 18:04 ` Chris Murphy
2017-01-23 0:47 ` Qu Wenruo
2017-01-23 21:14 ` Chris Murphy
2017-01-25 4:20 ` Qu Wenruo
2017-03-16 23:22 ` Chris Murphy
2017-03-17 0:54 ` Qu Wenruo
2017-11-10 23:16 ` Chris Murphy
2017-11-13 2:25 ` Su Yue
2017-11-13 3:37 ` Chris Murphy
2017-11-13 4:37 ` Qu Wenruo
2017-11-13 18:40 ` Chris Murphy
2017-11-13 18:41 ` Chris Murphy
2018-06-20 2:19 ` Chris Murphy
2018-06-20 2:38 ` Su Yue
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='CAJCQCtTdfD6=xWttk5D4JqLpzG9ZMxb-c=GopZPPNsLP6eHHpw@mail.gmail.com' \
--to=chris@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).