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: Thu, 10 Nov 2011 06:57:07 +0000 (UTC)	[thread overview]
Message-ID: <j9fsk3$f00$1@dough.gmane.org> (raw)
In-Reply-To: 4EBA33DB.2070409@parallels.com

Dmitry Olenin, Wed, 09 Nov 2011 17:03:39 +0900:

> On 11/09/2011 04:48 PM, Lubos Kolouch wrote:
>> 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?
> 
> Hello Lubos If you have a kernel that supports lzo (don't quite remember
> when it got in), why can't you?
> Absolutely nothing will happen, and only the new/updated files will be
> with lzo compression. You can remount on the fly switching b/w the two
> compression options without any problems.

Hello Dmitry,

By the way, this is interesting question to me - I mounted the filesystem
with -o compress=lzo, in dmesg showed btrfs: use lzo compression,

but - the lzo module was not loaded (not shown in lsmod - and yes, I have
it as a module).

When I do modprobe lzo, it shows there.

Isn't it a bit strange? So btrfs is using lzo module that was not loaded?
(and says so in the dmesg output)?

Thank you

Lubos


  reply	other threads:[~2011-11-10  6:57 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
2011-11-09  8:03                     ` Dmitry Olenin
2011-11-10  6:57                       ` Lubos Kolouch [this message]
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='j9fsk3$f00$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).