linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan K <shadow_7@gmx.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs filesystem show takes a long time
Date: Thu, 20 Sep 2018 08:24:25 +0200	[thread overview]
Message-ID: <2057542.pIGOqnJYbl@t460-skr> (raw)
In-Reply-To: <20180914112530.GV2154@twin.jikos.cz>

Hi,

> You may try to run the show command under strace to see where it blocks.
any recommendations for strace options?


On Friday, September 14, 2018 1:25:30 PM CEST David Sterba wrote:
> Hi,
> 
> thanks for the report, I've forwarded it to the issue tracker
> https://github.com/kdave/btrfs-progs/issues/148
> 
> The show command uses the information provided by blkid, that presumably
> caches that. The default behaviour of 'fi show' is to skip mount checks,
> so the delays are likely caused by blkid, but that's not the only
> possible reason.
> 
> You may try to run the show command under strace to see where it blocks.
> 

      reply	other threads:[~2018-09-20 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  9:03 btrfs filesystem show takes a long time Stefan K
2018-09-14 11:25 ` David Sterba
2018-09-20  6:24   ` Stefan K [this message]

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=2057542.pIGOqnJYbl@t460-skr \
    --to=shadow_7@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).