linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: commands like "du", "df", and "btrfs fs sync" hang
Date: Tue, 3 May 2016 08:48:14 +0200	[thread overview]
Message-ID: <20160503084814.3e355f56@jupiter.sol.kaishome.de> (raw)
In-Reply-To: CAD=QJKiQb0Ryedw+52pfZ-Tp0W9O0jPqxgGqxhY7b=U+2eP3wg@mail.gmail.com

Am Sun, 1 May 2016 20:39:31 -0400
schrieb Nicholas D Steeves <nsteeves@gmail.com>:

> On 1 May 2016 at 03:00, Kai Krakow <hurikhan77@gmail.com> wrote:
> > Hello!
> >
> > I'm not sure what triggeres this, neither if it is btrfs specific.
> > The filesystems have been recreated from scratch. Mainly during my
> > rsync backup (from btrfs to btrfs), but not necessarily limited to
> > rsync usage, my system experiences uninterruptable freezes of
> > commands like "df", "du", "btrfs fs sync", and probably more.  
> 
> Out of curiosity, does this occur if you don't create or delete
> snapshots, or if your backup script doesn't create or delete
> snapshots?  And when it occurs, are you able to go to another terminal
> and run a command that you don't use often, that definitely had to be
> read from disk, but that doesn't query any filesystem properties (eg:
> whois)?

I only create snapshots in the destination device, not on the source. I
could try disabling the snapshotting and see if it changes things.

It seems from my observation, that only programs querying disk free or
disk usage status hang, especially all of the btrfs subcommands doing
it hang, in addition to traditional programs like du and df. I think
also "btrfs sub delete" and friends hang. So your guess may very well
go into the right direction. Let me try. Coming back later...

-- 
Regards,
Kai

Replies to list-only preferred.


  reply	other threads:[~2016-05-03  6:50 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
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 [this message]
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=20160503084814.3e355f56@jupiter.sol.kaishome.de \
    --to=hurikhan77@gmail.com \
    --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).