From: Leen Besselink <leen@consolejunkie.net>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: df output wrong ?
Date: Mon, 05 Sep 2011 12:58:22 +0200 [thread overview]
Message-ID: <4E64AB4E.60609@consolejunkie.net> (raw)
In-Reply-To: <20110905101918.GK9907@carfax.org.uk>
On 09/05/2011 12:19 PM, Hugo Mills wrote:
>
> Snapshot/subvolume deletion is asynchronous -- it can take a while
> to happen. Try waiting a minute or two after the snapshot deletion and
> before looking at df -h.
>
> Hugo.
>
As I didn't see any disc activity, I thought it was done.
I just tried it again, it does seem to work the way you mentioned.
Thanks.
Just a quick question: would 'btrfs filesystem sync /path' help speed
that up ?
Like for example if a sys-admin sees that he's running out of space and
needs
to remove some old snapshots immediately.
Or when an automated backup first removes old snapshots to create room
for a new backup just before starting that backup.
prev parent reply other threads:[~2011-09-05 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 9:50 df output wrong ? Leen Besselink
2011-09-05 10:19 ` Hugo Mills
2011-09-05 10:58 ` Leen Besselink [this message]
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=4E64AB4E.60609@consolejunkie.net \
--to=leen@consolejunkie.net \
--cc=hugo@carfax.org.uk \
--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).