From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Chris Murphy" <lists@colorremedies.com>
Cc: "Chris Murphy" <lists@colorremedies.com>,
"Qu Wenruo" <quwenruo.btrfs@gmx.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re[6]: Rough (re)start with btrfs
Date: Mon, 06 May 2019 18:39:14 +0000 [thread overview]
Message-ID: <em9719915a-4d1f-4ab9-b14f-488b3cccd9f2@ryzen> (raw)
In-Reply-To: <CAJCQCtSdD32h_xTBVOxEZOp0XijqA0j=HsS5YgdePVhpdgtuRg@mail.gmail.com>
Hello,
>v2 is expected to become the default soon
That is good to hear.
>But from the sound of it Qu has enough
>information to maybe track down the v1 problem and fix it, and
>probably should be fixed as v1 is the default and is still supported
>and will be forever.
That's good to hear.
>>
>> For me, the question now is, whether we should chase this Bug or not. I
>> encountered it three times while filling a 8TB drive with 7TB. Now, I
>> have 1TB left and I am not sure I can reproduce, but I can try.
>
>I don't think it's necessary unless Qu specifically asks.
Let me know Qu.
>>you wouldn't want to constantly dump
>that amount of information into kernel message buffer and then burden
>the system logger with quite a lot of extraneous information.
I understand. Still, a a pitty.
>Once you have a reproducer, then you can change the scheduler and see
>if your reproduce steps still reproduce the problem.
I will try and let you know. It's not persistent.
Greetings,
Hendrik
>
next prev parent reply other threads:[~2019-05-06 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <em9eba60a7-2c0d-4399-8712-c134f0f50d4d@ryzen>
2019-05-02 23:40 ` Rough (re)start with btrfs Qu Wenruo
2019-05-03 5:41 ` Re[2]: " Hendrik Friedel
2019-05-03 6:05 ` Chris Murphy
2019-05-04 9:31 ` Re[4]: " Hendrik Friedel
2019-05-04 19:05 ` Chris Murphy
2019-05-06 18:39 ` Hendrik Friedel [this message]
2019-05-03 7:34 ` Qu Wenruo
2019-05-03 5:58 ` Chris Murphy
2019-05-03 5:52 ` Re[2]: " 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=em9719915a-4d1f-4ab9-b14f-488b3cccd9f2@ryzen \
--to=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--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).