From: "Fajar A. Nugraha" <list@fajar.net>
To: sander@humilis.net
Cc: Li Zefan <lizf@cn.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: make lzo the default compression scheme
Date: Fri, 27 May 2011 14:41:56 +0700 [thread overview]
Message-ID: <BANLkTikG4Af1fBExKHe+4UwVAm81U077Mg@mail.gmail.com> (raw)
In-Reply-To: <20110527073212.GA28453@attic.humilis.net>
On Fri, May 27, 2011 at 2:32 PM, Sander <sander@humilis.net> wrote:
> Li Zefan wrote (ao):
>> As the lzo compression feature has been established for quite
>> a while, we are now ready to replace zlib with lzo as the default
>> compression scheme.
>
> Please be aware that grub2 currently can't load files from a btrfs with
> lzo compression (on debian sid/experimental at least).
>
> Just found out the hard way after a kernel upgrade on a system with no
> separate /boot partition :-)
>
> Found this: https://bugs.archlinux.org/task/23901
IIRC what matters is compression actually used by the files.
If /boot/grub/* and kernel/initrd is not compressed, or compressed
with zlib, then grub2 can read it just fine, even when the filesystem
is usually mounted with -o compress=lzo (I'm using Ubuntu Natty).
I think the move to use lzo compression by default is a good thing, since:
- it's superior performance-wise to zlib
- btrfs is not really recommended (yet) for production uses, so it's
valid enough to assume users brave enough to use btrfs will know the
necessary workarounds (like having separate /boot, or temporary
remount with -o compress=zlib when upgrading kernel)
- even if by accident you ended with unbootable system due to lzo, you
can "fix" it using livecd and "btrfs filesystem defragment" to force
the needed files to be uncompressed/compressed with zlib.
--
Fajar
next prev parent reply other threads:[~2011-05-27 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:39 [PATCH] Btrfs: make lzo the default compression scheme Li Zefan
2011-05-27 7:32 ` Sander
2011-05-27 7:41 ` Fajar A. Nugraha [this message]
2011-05-28 5:12 ` C Anthony Risinger
2011-05-28 11:24 ` Chris Mason
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=BANLkTikG4Af1fBExKHe+4UwVAm81U077Mg@mail.gmail.com \
--to=list@fajar.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=sander@humilis.net \
/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).