Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Another defrag question
Date: Thu, 21 Feb 2013 23:50:53 +0800	[thread overview]
Message-ID: <20130221155052.GA4628@liubo.jp.oracle.com> (raw)
In-Reply-To: <51264146.3070504@petaramesh.org>

On Thu, Feb 21, 2013 at 04:46:14PM +0100, Swâmi Petaramesh wrote:
> Hi again,
> 
> Having numerous snapshots, I prefer to ask rather than take the risk of
> exploding my storage space, better safe than sorry ;-)
> 
> "man btrfs" states :
> 
> « NOTE: defragmenting with kernels up to 2.6.37 will unlink COW-ed
> copies of data, don't use it if  you  use  snapshots,  have 
> deduplicated  your  data  or  made  copies with cp --reflink. »
> 
> I use :
> # uname -r
> 3.5.0-24-generic
> 
> ...So should I expect that defraging my BTRFS will be smart enough not
> to uncow my snapshots ? Is it actually able to defrag both the file and
> its snapshots altogether, keeping all this as a single physical copy of
> the defragged data ?

Well, there is already a patch which addresses your concern and it's
'snapshot-aware defrag' feature and now in v6, it's not merged yet.

thanks,
liubo

> 
> TIA.
> 
> -- 
> Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
> Ne cherchez pas : Je ne suis pas sur Facebook.
> 
> --
> 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

  reply	other threads:[~2013-02-21 15:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 15:46 Another defrag question Swâmi Petaramesh
2013-02-21 15:50 ` Liu Bo [this message]
2013-02-21 15:55   ` Swâmi Petaramesh
2013-02-21 15:54 ` Calvin Walton
2013-02-21 16:01   ` Swâmi Petaramesh
2013-02-21 16:09     ` Blair Zajac
2013-02-21 16:38     ` Hugo Mills
2013-02-21 17:03       ` Swâmi Petaramesh
2013-02-21 17:25         ` Hugo Mills
2013-02-21 17:47           ` Swâmi Petaramesh
2013-02-21 20:46             ` Hugo Mills
2013-02-21 20:58             ` Bardur Arantsson
2013-02-21 21:56               ` David Sterba
2013-02-22  5:55                 ` Bardur Arantsson
2013-02-21 21:31             ` Johannes Hirte

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=20130221155052.GA4628@liubo.jp.oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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