From: Anthony Roberts <btrfs-devel@arbitraryconstant.com>
To: Josef Bacik <josef@redhat.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: dynamically remove unused block groups
Date: Tue, 30 Nov 2010 21:53:41 -0700 [thread overview]
Message-ID: <970f54e0098c313a4b780b2356734592@arbitraryconstant.com> (raw)
In-Reply-To: <20101130193512.GB2577@localhost.localdomain>
Hello,
What happens in the event the filesystem has mostly been cleared out,
but there's a few things left? For example, several of the chunks might
be at very low usage, but not zero. Would the user be able to defragment
the filesystem to cause these chunks to be consolidated?
Regards,
-Anthony
> Yeah 2 things to keep in mind, 1 if you have snapshots you are likely
> to not see
> data free'd up the way you expect it. The other thing is that
> because
> everything is COW we can't allocate the newly free'd space until the
> transaction
> commits, so you may have to wait ~30 seconds or run sync to force the
> transaction to commit before you see your space actually free'd up.
> Thanks,
>
> Josef
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-01 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 16:46 [PATCH] Btrfs: dynamically remove unused block groups Josef Bacik
2010-11-30 17:37 ` Josh Berry
2010-11-30 19:01 ` Josef Bacik
2010-11-30 19:31 ` Josh Berry
2010-11-30 19:35 ` Josef Bacik
2010-12-01 4:53 ` Anthony Roberts [this message]
2010-12-01 8:11 ` Josef Bacik
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=970f54e0098c313a4b780b2356734592@arbitraryconstant.com \
--to=btrfs-devel@arbitraryconstant.com \
--cc=josef@redhat.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).