From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs qgroup destroy -> ERROR: unable to create quota group: Device or resource busy
Date: Fri, 09 Aug 2013 13:56:19 +0800 [thread overview]
Message-ID: <52048483.1010809@cn.fujitsu.com> (raw)
In-Reply-To: <20130809133933.2fbfc6e4@virtall.com>
Hello,
On 08/09/2013 01:39 PM, Tomasz Chmielewski wrote:
> I'm using qgroups and have created a few hundreds of subvolumes in the
> past.
>
> It seems that btrfs automatically assigns a qgroup to newly created
> snapshot/subvolume, but does not destroy the qgroup when the subvolume
> is deleted.
This should be implemented. And will soon.
>
> So I've tried to destroy the unused qgroups, with mixed success. I was
> able to destroy most of them, but some are still failing, i.e.:
>
> # btrfs qgroup destroy 4494 /mnt/lxc1
> ERROR: unable to create quota group: Device or resource busy
Just remove qgroup(4494)'s parent qgroup. then it can be removed.
Anyway, i think this is unnecessary.
Thanks,
Wang
>
>
> Note the negative number here, but I also have qgroups with both
> positive numbers, which I'm not able to destroy as well:
>
> # btrfs qgroup show /mnt/lxc1 | grep 4494
> 0/4494 839516160 -69632
>
>
> qgroup 4494 is not used by any subvolume:
>
> # btrfs sub list /mnt/lxc1 | grep 4494
>
>
> I did run "btrfs quota rescan" for this filesystem, hoping it will fix
> the problem, but it didn't.
>
>
> Any advice?
>
>
next prev parent reply other threads:[~2013-08-09 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 5:39 btrfs qgroup destroy -> ERROR: unable to create quota group: Device or resource busy Tomasz Chmielewski
2013-08-09 5:56 ` Wang Shilong [this message]
2013-08-09 6:07 ` Tomasz Chmielewski
2013-08-09 6:08 ` Wang Shilong
2013-08-09 6:42 ` Tomasz Chmielewski
2013-08-09 6:56 ` Wang Shilong
2013-08-09 7:47 ` Tomasz Chmielewski
2013-08-09 12:47 ` Wang Shilong
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=52048483.1010809@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tch@virtall.com \
/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).