linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Setting options permanently?
Date: Mon, 30 Jan 2012 13:57:49 +0800	[thread overview]
Message-ID: <4F26315D.30905@cn.fujitsu.com> (raw)
In-Reply-To: <pan.2012.01.28.03.32.23@cox.net>

>> I currently don't see how to repair this afterwards without removing the
>> uncompressed files and writing new ones, which on the other hand spoils
>> hte memory saving effect of using snapshots instead of copies.
> 
> A rebalance is the usual way of handling such things, since that rewrites 
> every chunk, taking account of current mount options, etc.  If I've been 
> reading correctly, a defrag should handle it now as well, altho that used 
> to break snapshots/cow/reflink-copies, but I /think/ I read that with 3.2 
> (or was it 3.3-rc1) it doesn't, any more.
> 

Rebalance won't do the trick, but defrag can. And defrag still breaks
snapshots, which I'm working on.

  parent reply	other threads:[~2012-01-30  5:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 15:03 Setting options permanently? Hadmut Danisch
2012-01-27 23:20 ` Chester
2012-01-28  0:49   ` Hadmut Danisch
2012-01-28  3:32     ` Duncan
2012-01-28  6:05       ` Ben Klein
2012-01-28  8:23         ` Roman Mamedov
2012-01-28  9:24           ` Ben Klein
2012-01-28 10:55           ` Duncan
2012-01-30  5:57       ` Li Zefan [this message]
2012-01-28 12:07     ` Fajar A. Nugraha
2012-01-30  7:18     ` Sander
2012-01-30  7:49 ` Li Zefan

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=4F26315D.30905@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=1i5t5.duncan@cox.net \
    --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).