linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to remount btrfs without compression?
Date: Wed, 9 Nov 2011 07:48:56 +0000 (UTC)	[thread overview]
Message-ID: <j9db98$gbt$1@dough.gmane.org> (raw)
In-Reply-To: 4EB9D0D9.1000009@parallels.com

dima, Wed, 09 Nov 2011 10:01:13 +0900:

> On 11/09/2011 12:12 AM, Chris Mason wrote:
>> On Tue, Nov 08, 2011 at 10:01:51AM -0500, Chris Mason wrote:
>>> On Tue, Nov 08, 2011 at 11:00:42AM +0900, dima wrote:
>>>> On 11/08/2011 10:54 AM, Eric Griffith wrote:
>>>>> On 11/7/2011 8:52 PM, Fajar A. Nugraha wrote:
>>>>>> On Tue, Nov 8, 2011 at 8:06 AM, Eric
>>>>>> Griffith<egriffith92@gmail.com> wrote:
>>>>>>> Edit your fstab, remove the compress flag, reboot. Tell btrfs to
>>>>>>> rebalance the system,
>>>>>>> reboot again. And I -THINK- that'll decompress all the files
>>>>>>
>>>>>> I think the original question was how to force uncompressed mode,
>>>>>> whether specific to a file or to a whole filesystem, without having
>>>>>> to reboot :)
>>>>>>
>>>>>> AFAIK there's no way to do that.
>>>>>>
>>>>>>
>>>>> Whoops! Misunderstood the question haha. Yeah, as far as
>>>>> decompressing just a single file; from what I've read, thats
>>>>> impossible.
>>>>
>>>>
>>>> Eric, Fajar,
>>>> Thanks. Understood.
>>>>
>>>> Yes, it is possible to remove the compress flag from fstab, reboot
>>>> and even do not do any defragmentation/rebalancing - just re-save the
>>>> file and it will be saved uncompressed. This works. But only with
>>>> reboot...
>>>
>>> chattr -c on the file should work (followed by defrag or rewriting the
>>> file).  I just retested and it seems to be broken right now.
>>>
>>> I'll track it down.
>>
>> Ok, I had forgotten.  chattr -c clears the compression flag bug doesn't
>> set the no compress flag.  We looks like we need to patch chattr for
>> this.
>>
>> -chris
>>
>>
> 
> Just for the record - I could find a solution thanks to the btrfs wiki
> being online again. In Gotchas it says
> 
> mount -o nodatacow also disables compression
> 
> and indeed it does. Remounting with this option and re-saving the file
> makes it uncompressed. However, I could not find how to remount the
> filesystem afterwards without nodatacow.
> 
> ~dima

Sorry for possibly OT question - when I have historical btrfs system
mounted with zlib compression,

can I remount it with lzo ? What will happen? Will the COW be broken
and the files taking duplicate space? Or will the Universe explode and
be replaced with something even more bizzare?

Thank you 

Lubos


  reply	other threads:[~2011-11-09  7:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  0:53 How to remount btrfs without compression? dima
2011-11-07 12:19 ` Martin Steigerwald
2011-11-08  0:55   ` dima
2011-11-08  1:06     ` Eric Griffith
2011-11-08  1:52       ` Fajar A. Nugraha
2011-11-08  1:54         ` Eric Griffith
2011-11-08  2:00           ` dima
2011-11-08 15:01             ` Chris Mason
2011-11-08 15:12               ` Chris Mason
2011-11-09  1:01                 ` dima
2011-11-09  7:48                   ` Lubos Kolouch [this message]
2011-11-09  8:03                     ` Dmitry Olenin
2011-11-10  6:57                       ` Lubos Kolouch
2011-11-10  7:04                         ` Dmitry Olenin
2011-11-09  8:04                     ` Fajar A. Nugraha
2011-11-09 13:01                       ` Chris Mason
2011-11-10  0:11                   ` David Sterba
2011-11-10  2:23                     ` dima
2011-11-11 13:29                       ` dima

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='j9db98$gbt$1@dough.gmane.org' \
    --to=lubos.kolouch@gmail.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).