archive mirror
 help / color / mirror / Atom feed
From: waxhead <>
To: Btrfs BTRFS <>
Subject: Switching from spacecache v1 to v2
Date: Sat, 31 Oct 2020 01:27:57 +0100	[thread overview]
Message-ID: <> (raw)

A couple of months ago I asked on IRC how to properly switch from 
version 1 to version 2 of the space cache. I also asked if the space 
cache v2 was considered stable.
I only remember what we talked about, and from what I understood it was 
not as easy to switch as the wiki may seem to indicate.

We run a box with a btrfs filesystem at 19TB, 9 disks, 11 subvolumes 
that contains about 6.5 million files (and this number is growing).

The filesystem has always been mounted with just the default options.

Performance is slow, and it improved when I moved the bulk of the files 
to various subvolumes for some reason. The wiki states that performance 
on very large filesystems (what is considered large?) may degrade 

I would like to try v2 of the space cache to see if that improves speed 
a bit.

So is space cache v2 safe to use?!
How do I make the switch properly?

             reply	other threads:[~2020-10-31  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31  0:27 waxhead [this message]
2020-11-01 17:49 ` Zygo Blaxell
2020-11-02  5:48   ` A L
2020-11-02 14:40     ` Zygo Blaxell
2020-11-02 17:03   ` waxhead

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: Switching from spacecache v1 to v2' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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