From: Hugo Mills <hugo@carfax.org.uk>
To: Astro Xe <astroxeu@yahoo.it>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs fi df output is not updated in a timely manner after subvolumes have been deleted
Date: Tue, 20 May 2014 15:33:05 +0100 [thread overview]
Message-ID: <20140520143305.GA1756@carfax.org.uk> (raw)
In-Reply-To: <1400593810.31610.YahooMailNeo@web172206.mail.ir2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Tue, May 20, 2014 at 02:50:10PM +0100, Astro Xe wrote:
>
> On my box, the "used" value in the output of "btrfs filesystem df" is not updated in a timely manner, after that one or more subvolumes have been deleted. I need to execute "btrfs filesystem sync", in order to update the value.
>
> How do I fix this? Or, could someone fix this in btrfs-progs, please?
I've not tested this, but I think you need one of the two -c/-C
options to btrfs sub del, which perform a synchronous delete. Once the
command returns, you can be assured that the subvolume has actually
been deleted and any extents freed up.
> I suspect the cause is that subvolumes are marked immediately as deleted, but cleaned up at a later time, is this right?
Correct.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Great oxymorons of the world, no. 10: Business Ethics ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-05-20 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 13:50 btrfs fi df output is not updated in a timely manner after subvolumes have been deleted Astro Xe
2014-05-20 14:26 ` Russell Coker
2014-05-20 14:33 ` Hugo Mills [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-20 13:46 Astro Xe
2014-05-20 16:51 ` Calvin Walton
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=20140520143305.GA1756@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=astroxeu@yahoo.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.