From: Christopher James Halse Rogers <chris@cooperteam.net>
To: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] time of mounting filesystem with high number of dirs
Date: Fri, 09 Sep 2016 12:07:18 +1000 [thread overview]
Message-ID: <1473386838.30693.4@mail.cooperteam.net> (raw)
In-Reply-To: <20160909015629.356sy3q4gg35szbn@kmo-pixel>
On Fri, Sep 9, 2016 at 11:56 AM, Kent Overstreet
<kent.overstreet@gmail.com> wrote:
> On Wed, Sep 07, 2016 at 01:12:12PM -0800, Kent Overstreet wrote:
>> So, right now we're checking i_nlinks on every mount - mainly the
>> dirents
>> implementation predates the transactional machinery we have now.
>> That's almost
>> definitely what's taking so long, but I'll send you a patch to
>> confirm later.
>
> I just pushed a patch to add printks for the various stages of
> recovery: use
> mount -o verbose_recovery to enable.
>
> How many files does this filesystem have? (df -i will tell you).
>
> As another data point, on my laptop mounting takes half a second -
> smallish
> filesystem though, 47 gb of data and 711k inodes (and it's on an
> SSD). My
> expectation is that mount times with the current code will be good
> enough as
> long as you're using SSDs (or tiering, where tier 0 is SSD) - but I
> could use
> more data points.
FWIW, I've got a tier 0 SSD in front of two 3TB HDDs, 1.8M inodes and
150GB used, and that takes 380ms to mount if systemd-analyse is to be
trusted.
next prev parent reply other threads:[~2016-09-09 2:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 20:09 [bcachefs] time of mounting filesystem with high number of dirs Marcin
2016-09-07 21:12 ` Kent Overstreet
2016-09-09 1:56 ` Kent Overstreet
2016-09-09 2:07 ` Christopher James Halse Rogers [this message]
2016-09-09 7:52 ` Marcin Mirosław
2016-09-09 9:00 ` Kent Overstreet
2016-09-12 12:59 ` Marcin
2016-09-13 2:35 ` Kent Overstreet
2016-10-05 12:51 ` Marcin Mirosław
2016-10-06 13:01 ` Kent Overstreet
2016-10-18 12:14 ` [bcachefs] time of mounting filesystem with high number of dirs aka ageing filesystem Marcin Mirosław
2016-10-18 12:45 ` Kent Overstreet
2016-10-18 12:51 ` Marcin Mirosław
2016-10-18 13:04 ` Kent Overstreet
2016-10-18 13:13 ` Marcin Mirosław
2016-10-18 13:19 ` Kent Overstreet
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=1473386838.30693.4@mail.cooperteam.net \
--to=chris@cooperteam.net \
--cc=linux-bcache@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