From: dima <dolenin@parallels.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: How to remount btrfs without compression?
Date: Fri, 11 Nov 2011 22:29:51 +0900 [thread overview]
Message-ID: <4EBD234F.4050705@parallels.com> (raw)
In-Reply-To: <4EBB35A7.8080909@parallels.com>
On 11/10/2011 11:23 AM, dima wrote:
> On 11/10/2011 09:11 AM, David Sterba wrote:
>> On Wed, Nov 09, 2011 at 10:01:13AM +0900, dima wrote:
>>> 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.
>>
>> I saw this mentioned on irc today (that nodatacow diasables
>> compression). There is a way how to turn off compression on a file --
>> with help of the NOCOW _file_ attribute, ie. you don't have to remount.
>>
>> * create the file, compression enabled
>> * set NOCOW (with the attached single-purpose nocow.c utility)
>> * btrfs fi defrag the_file
>>
>> Make sure you have enough free space for the uncompressed file size. You
>> can compare the extent layout before and after the defrag with
>> "filefrag -v" .
>
>
> Hello David,
>
> Thank you, I will try it out tonight. Is there any way to see if nocow
> attribute was set on a particular file, and is there any way to unset it?
Hi David
I tried the nocow utility. It worked.
First I made sure to re-save the syslinux.cfg file while btrfs was
mounted with lzo to ensure that it is compressed, then I set the NOCOW
flag with your utility. Then I checked fragmentation of the file and
since it was a small one it was not fragmented. So when I ran btrfs fi
defrag syslinux.cfg it did not have any effect and file was not
uncompressed. Then I simply re-saved the file and it got uncompressed
fine since bootloader could read it on reboot.
thanks
prev parent reply other threads:[~2011-11-11 13:29 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
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 [this message]
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=4EBD234F.4050705@parallels.com \
--to=dolenin@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.