From: Alin Dobre <alin.dobre@elastichosts.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Subvolume creation returns file exists
Date: Thu, 28 Nov 2013 10:01:31 +0000 [thread overview]
Message-ID: <5297147B.7030904@elastichosts.com> (raw)
In-Reply-To: <528630D6.5090103@elastichosts.com>
It seems that the problem was that we didn't delete the corresponding
qgroup when deleting the subvolume, which was filling the metadata with
unused information. Removing all the stale qgroups fixes the problem and
allows subsequent subvolume creation without any quota disable/enable
action. Also, we are now automatically deleting the corresponding qgroup
after the subvolume is removed.
Cheers,
Alin.
next prev parent reply other threads:[~2013-11-28 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:33 Subvolume creation returns file exists Alin Dobre
2013-11-15 15:27 ` Hugo Mills
2013-11-15 16:39 ` cwillu
2013-11-15 16:07 ` Duncan
2013-11-16 18:57 ` Duncan
2013-11-18 13:22 ` Alin Dobre
2013-11-28 10:01 ` Alin Dobre [this message]
2013-11-29 5:40 ` 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=5297147B.7030904@elastichosts.com \
--to=alin.dobre@elastichosts.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).