From: Stefan K <shadow_7@gmx.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs filesystem show takes a long time
Date: Fri, 14 Sep 2018 11:03:24 +0200 [thread overview]
Message-ID: <3275334.7C4KuSQybz@t460-skr> (raw)
Dear Maintainer,
the command btrfs fi show takes too much time:
time btrfs fi show
Label: none uuid: 513dc574-e8bc-4336-b181-00d1e9782c1c
Total devices 2 FS bytes used 2.34GiB
devid 1 size 927.79GiB used 4.03GiB path /dev/sdv2
devid 2 size 927.79GiB used 4.03GiB path /dev/sdar2
real 12m59.763s
user 0m0.008s
sys 0m0.044s
time btrfs fi show
Label: none uuid: 513dc574-e8bc-4336-b181-00d1e9782c1c
Total devices 2 FS bytes used 2.34GiB
devid 1 size 927.79GiB used 4.03GiB path /dev/sdv2
devid 2 size 927.79GiB used 4.03GiB path /dev/sdar2
real 6m22.498s
user 0m0.012s
sys 0m0.024s
time btrfs fi show
Label: none uuid: 513dc574-e8bc-4336-b181-00d1e9782c1c
Total devices 2 FS bytes used 2.34GiB
devid 1 size 927.79GiB used 4.03GiB path /dev/sdv2
devid 2 size 927.79GiB used 4.03GiB path /dev/sdar2
real 6m19.796s
user 0m0.012s
sys 0m0.024s
Maybe its related to that I've some harddisk in my system:
ls /dev/disk/by-path/ |grep -v part |wc -l
44
This is also a known Debian Bug #891717
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-5-amd64 (SMP w/20 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages btrfs-progs depends on:
ii e2fslibs 1.43.4-2
ii libblkid1 2.29.2-1
ii libc6 2.24-11+deb9u1
ii libcomerr2 1.43.4-2
ii liblzo2-2 2.08-1.2+b2
ii libuuid1 2.29.2-1
ii zlib1g 1:1.2.8.dfsg-5
next reply other threads:[~2018-09-14 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 9:03 Stefan K [this message]
2018-09-14 11:25 ` btrfs filesystem show takes a long time David Sterba
2018-09-20 6:24 ` Stefan K
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=3275334.7C4KuSQybz@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).