Am Thu, 5 May 2016 08:35:37 +0200 schrieb Kai Krakow <hurikha...@gmail.com>:
> Am Tue, 3 May 2016 08:48:14 +0200 > schrieb Kai Krakow <hurikha...@gmail.com>: > > > Am Sun, 1 May 2016 20:39:31 -0400 > > schrieb Nicholas D Steeves <nstee...@gmail.com>: > > > > > On 1 May 2016 at 03:00, Kai Krakow <hurikha...@gmail.com> > > > wrote: > [...] > > > > > > 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... > > With the snapshot and sync related bits disabled in my script, I no > longer experience freezing df/du/... commands. Ah well, I still do - it just triggers much less often. But I can track it down to the automounter now: As soon as I stop the automounter of my backup device, du/df/etc no longer hang. Still I'm not sure if the problem is originating from btrfs or autofs itself. -- Regards, Kai Replies to list-only preferred. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
