From: Hugo Mills <hugo@carfax.org.uk>
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 17:21:04 +0100 [thread overview]
Message-ID: <20111013162104.GG21931@carfax.org.uk> (raw)
In-Reply-To: <CAJ1PRSmDmd4mrUaQAhjCt1SMtVaBVxq3dCVjCuT20Y4Wf+Ch+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Thu, Oct 13, 2011 at 06:14:03PM +0200, krzf83@gmail.com wrote:
> I'm wondering is space really freed after deleting large subvolume?
Yes, although if you have snapshots, you may not recover very much
space, as [some of] the data on the subvolume may still be in use by
other snapshots.
> Will space be immediately available to other data like other
> subvolumes?
No, subvolume deletion is done in the background, and the space
recovered will be returned for use relatively slowly. This is because
the FS has to go through the metadata, updating reference counts for
each extent in the subvolume to work out whether the space can be
recovered or not.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Klytus! Are your men on the right pills? Maybe you should ---
execute their trainer!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-10-13 16:21 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 [this message]
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
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=20111013162104.GG21931@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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