From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: commands like "du", "df", and "btrfs fs sync" hang
Date: Sun, 1 May 2016 23:49:44 +0000 (UTC) [thread overview]
Message-ID: <pan$cd18$90efec60$149cab40$cd3d9864@cox.net> (raw)
In-Reply-To: 20160501185418.5a148cdd@jupiter.sol.kaishome.de
Kai Krakow posted on Sun, 01 May 2016 18:54:18 +0200 as excerpted:
> It affects all file systems. The "btrfs fi sync" is used to finish my
> rsync backup and ensure everything is written before I'm trying to
> unmount it or the system goes back to sleep.
>
> "df" and friends also freeze on tmp (ramdisk) fs and vfat fs (my EFI
> boot partition).
That's just weird, there. df on tmpfs triggers a stall as well? Weird
to the point I wonder if you're seeing a general block layer bug... only
involving btrfs if btrfs is somehow fowling up the block layer for
everyone else as well. Whatever it is, it's obviously far different than
my first guess, which now looks ridiculously wrong. Oh, well...
But given that I've seen no other reports of it, I'd consider the things
that are unique to your kernel config compared to others running btrfs.
The first thing off the top of my head, bcache. Do you happen to follow
the bcache list (presuming it has one) as well? Given this new
information and the contrast with others running btrfs, I'd wonder if
they've had similar reported.
If I understand correctly, with bcache, you can't entirely turn it off or
bypass it as the filesystems are installed on top of it. Have you tried
tinkering with its writeback settings? Alternatively, if you have the
space/time to test, try creating a new btrfs with the same options, etc,
but without the bcache layer, and see if it gives you similar behavior in
terms of even df of a tmpfs hanging like that, of course without the
positive effects of bcache as well, tho.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-01 23:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 7:00 commands like "du", "df", and "btrfs fs sync" hang Kai Krakow
2016-05-01 12:47 ` Duncan
2016-05-01 13:54 ` Mike Fleetwood
2016-05-01 23:16 ` Duncan
2016-05-01 16:54 ` Kai Krakow
2016-05-01 23:22 ` Duncan
2016-05-01 23:49 ` Duncan [this message]
2016-05-02 13:19 ` Austin S. Hemmelgarn
2016-05-03 6:44 ` Kai Krakow
2016-05-02 0:23 ` Duncan
2016-05-02 13:13 ` Austin S. Hemmelgarn
2016-05-03 15:09 ` Duncan
2016-05-02 0:39 ` Nicholas D Steeves
2016-05-03 6:48 ` Kai Krakow
2016-05-05 6:35 ` Kai Krakow
2016-05-07 11:40 ` Kai Krakow
2016-05-09 17:13 ` Nicholas D Steeves
2016-05-09 18:20 ` Kai Krakow
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 10:22 Kai Krakow
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='pan$cd18$90efec60$149cab40$cd3d9864@cox.net' \
--to=1i5t5.duncan@cox.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).