linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Hanging after frequent use of systemd-nspawn --ephemeral
Date: Sun, 14 Jan 2018 16:30:38 +0000 (UTC)	[thread overview]
Message-ID: <pan$46776$62a5e0fc$bbee4809$9a4f8e9d@cox.net> (raw)
In-Reply-To: 8c9933e1-f694-a513-83ca-33fcb503b7e8@gmx.com

Qu Wenruo posted on Sun, 14 Jan 2018 10:27:40 +0800 as excerpted:

> Despite of that, did that really hangs?
> Qgroup dramatically increase overhead to delete a subvolume or balance
> the fs.
> Maybe it's just a little slow?

Same question about the "hang" here.

Note that btrfs is optimized to make snapshot creation fast, while 
snapshot deletion has to do more work to clean things up.  So even 
without qgroup enabled, deletion can take a bit of time (much longer than 
creation, which should be nearly instantaneous in human terms) if there's 
a lot of relinks and the like to clean up.

And qgroups makes btrfs do much more work to track that as well, so as Qu 
says, that'll make snapshot deletion take even longer, and you probably 
want it disabled unless you actually need the feature for something 
you're doing.

-- 
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


  reply	other threads:[~2018-01-14 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14  1:36 Hanging after frequent use of systemd-nspawn --ephemeral Johannes Ernst
2018-01-14  2:27 ` Qu Wenruo
2018-01-14 16:30   ` Duncan [this message]
2018-01-14 20:17   ` Johannes Ernst
2018-01-15  0:48     ` Qu Wenruo
2018-01-15  0:58       ` Johannes Ernst
2018-01-15  1:34         ` Qu Wenruo
2018-01-15  1:47           ` Johannes Ernst
2018-01-15  1:55             ` Qu Wenruo
2018-01-14 20:18   ` Johannes Ernst

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$46776$62a5e0fc$bbee4809$9a4f8e9d@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).