From: Roman Mamedov <rm@romanrm.ru>
To: "krzf83@gmail.com " <krzf83@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: is space really freed after deleting large subvolume?
Date: Thu, 13 Oct 2011 22:29:44 +0600 [thread overview]
Message-ID: <20111013222944.16efb3f3@natsu> (raw)
In-Reply-To: <CAJ1PRSmDmd4mrUaQAhjCt1SMtVaBVxq3dCVjCuT20Y4Wf+Ch+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Thu, 13 Oct 2011 18:14:03 +0200
"krzf83@gmail.com " <krzf83@gmail.com> wrote:
> I'm wondering is space really freed after deleting large subvolume?
> Will space be immediately available to other data like other
> subvolumes?
Currently there seems to be no way to ensure it is instantly available, or to be precise, the only way to get that is to unmount the FS and mount it again. Not sync, not "btrfs fi sync" ensure that all cleanup is complete before they return. Only umount does, and it can take a very long time if you have deleted a large (differing a lot) subvolume just before that.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-13 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 16:14 is space really freed after deleting large subvolume? krzf83@gmail.com
2011-10-13 16:21 ` Hugo Mills
2011-10-13 16:57 ` krzf83@gmail.com
2011-10-13 18:06 ` krzf83@gmail.com
2011-10-13 19:22 ` krzf83@gmail.com
2011-10-13 20:01 ` David Pottage
2011-10-13 21:03 ` krzf83@gmail.com
2011-10-14 17:26 ` Maciej Marcin Piechotka
2011-10-13 16:29 ` Roman Mamedov [this message]
2011-10-14 5:17 ` krzf83@gmail.com
2011-10-14 8:45 ` Hugo Mills
2011-10-14 17:12 ` Bruce Guenter
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=20111013222944.16efb3f3@natsu \
--to=rm@romanrm.ru \
--cc=krzf83@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