From: Christian Rohmann <crohmann@netcologne.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Progress indicator when (slowly) mounting a btrfs filesystem?
Date: Mon, 1 Feb 2016 15:03:10 +0100 [thread overview]
Message-ID: <56AF659E.2080009@netcologne.de> (raw)
In-Reply-To: <CAJCQCtQ6RwedgskkT9EECdj_2aZVEZZhfNwvkqOWztzk-MyKTg@mail.gmail.com>
Hey Chris,
On 01/28/2016 12:47 AM, Chris Murphy wrote:
> Might be a bug, but more likely might be a lack of optimization. If it
> eventually mounts without errors that's a pretty good plus. Lots of
> file systems can't handle power failures well at all.
So what and how should I go about profiling such a long running mount in
order to help finding point where optimization is needed the most then?
Just as a side note: I don't think it's your own expectation to be like
all those other file systems ;-)
Regards
Christian
next prev parent reply other threads:[~2016-02-01 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:24 Progress indicator when (slowly) mounting a btrfs filesystem? Christian Rohmann
2016-01-27 21:00 ` bbrendon
2016-01-27 23:47 ` Chris Murphy
2016-02-01 14:03 ` Christian Rohmann [this message]
2016-02-01 14:19 ` Austin S. Hemmelgarn
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=56AF659E.2080009@netcologne.de \
--to=crohmann@netcologne.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).