From: DanglingPointer <danglingpointerexception@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: migrating to space_cache=2 and btrfs userspace commands
Date: Wed, 14 Jul 2021 16:54:24 +1000 [thread overview]
Message-ID: <1333ad7a-941d-aead-6e5f-06e321c84feb@gmail.com> (raw)
In-Reply-To: <889c88ad-f51a-5b1f-3613-0b78af77477c@gmx.com>
Yep that's what I'm referring to here:
https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs(5)
Thanks for the prompt respone Qu!
So just to confirm, our scheduled cron jobs to scrub will still work
with space_cache=v2?
On 14/7/21 4:05 pm, Qu Wenruo wrote:
>
>
> On 2021/7/14 下午1:44, Chris Murphy wrote:
>> On Tue, Jul 13, 2021 at 10:59 PM Qu Wenruo <quwenruo.btrfs@gmx.com>
>> wrote:
>>>
>>>
>>>
>>> On 2021/7/13 下午11:38, DanglingPointer wrote:
>>
>>>> 2. If we use space_cache=v2, is it indeed still the case that the
>>>> "btrfs" command will NOT work with the filesystem?
>>>
>>> Why would you think "btrfs" won't work on a btrfs?
>>>
>>
>> Maybe this?
>>
>> man 5 btrfs, space_cache includes:
>>
>> The btrfs(8) command currently only has read-only support for v2. A
>> read-write command may be run on a v2 filesystem by clearing the
>> cache, running the command, and then remounting with space_cache=v2.
>>
>
> Oh, that's only for offline tools writing into the fs, namingly "btrfs
> check --repair" and "mkfs.btrfs -R"
>
> And I believe that sentence is now out-of-date after btrfs-progs v4.19,
> which pulls all the support for write time free space tree (v2 space
> cache).
>
> I'll soon send out a patch to fix that.
>
> Thanks,
> Qu
next prev parent reply other threads:[~2021-07-14 6:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 15:38 migrating to space_cache=2 and btrfs userspace commands DanglingPointer
2021-07-14 4:59 ` Qu Wenruo
2021-07-14 5:44 ` Chris Murphy
2021-07-14 6:05 ` Qu Wenruo
2021-07-14 6:54 ` DanglingPointer [this message]
2021-07-14 7:07 ` Qu Wenruo
2021-07-14 7:18 ` DanglingPointer
2021-07-14 7:45 ` Qu Wenruo
2021-07-15 16:40 ` DanglingPointer
2021-07-15 22:13 ` Qu Wenruo
2021-07-15 17:51 ` Joshua
2021-07-16 12:42 ` DanglingPointer
2021-07-16 12:59 ` Qu Wenruo
2021-07-16 13:23 ` DanglingPointer
2021-07-16 20:33 ` Joshua Villwock
2021-07-16 23:00 ` 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=1333ad7a-941d-aead-6e5f-06e321c84feb@gmail.com \
--to=danglingpointerexception@gmail.com \
--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).