From: Roman Mamedov <rm@romanrm.net>
To: Joakim <ahoj79@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Speed up mount time?
Date: Thu, 24 Nov 2022 03:01:50 +0500 [thread overview]
Message-ID: <20221124030150.0b064549@nvm> (raw)
In-Reply-To: <CAFka4xNPJby02JcK+immNU+AL6w-=iH7tNB4ZjULoYxnwG7U+Q@mail.gmail.com>
On Wed, 23 Nov 2022 13:33:17 +0100
Joakim <ahoj79@gmail.com> wrote:
> Initially mount times were quite long, about 10 minutes. But after i
> did run a defrag with -c option on machine B the mount time increased
> to over 30 minutes. This volume has a little over 100 TB stored.
>
> How come the mount time increased by this?
With compression each file now has to be split into extents each at most 128K
long, which means there are much more extents to keep track of than before.
> And is there any way to decrease the mount times? 10 minutes is long
> but acceptable, while 30 minutes is way too long.
>
> Advice would be highly appreciated. :)
It is unfortunate that you use the bare sdb device, if you used LVM, you could
easily add an SSD and deploy LVM caching in writethrough mode (or a RAID1 of
SSDs and use the writeback mode). In my experience LVM caching of HDD based
storage to SSDs improves mount times of Btrfs really by a lot.
There have been a number of attempts to implement Btrfs native storage tiering
of HDDs vs SSDs (storing metadata on the latter), such as [1], but none have
made it so far, and the patches from 2020 probably no longer apply.
[1]https://lwn.net/ml/linux-btrfs/20201029053556.10619-1-wangyugui@e16-tech.com/
--
With respect,
Roman
next prev parent reply other threads:[~2022-11-23 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 12:33 Speed up mount time? Joakim
2022-11-23 21:44 ` Qu Wenruo
2022-11-25 8:55 ` Joakim
2022-11-25 9:03 ` Qu Wenruo
2022-11-25 9:22 ` Joakim
2022-11-25 22:25 ` Torbjörn Jansson
2022-12-13 0:30 ` kenneth topp
2022-11-23 22:01 ` Roman Mamedov [this message]
2022-11-25 8:57 ` Joakim
2022-11-23 22:15 ` Forza
2022-11-25 8:58 ` Joakim
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=20221124030150.0b064549@nvm \
--to=rm@romanrm.net \
--cc=ahoj79@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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