From: "Fajar A. Nugraha" <list@fajar.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Compression: per filesystem, or per subvolume?
Date: Tue, 10 May 2011 16:51:34 +0700 [thread overview]
Message-ID: <BANLkTinDYX_twMsEDg0QgRrVmKKY_YDm+g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikS522HZBv+05md-okRey37aZd6gA@mail.gmail.com>
On Sun, May 8, 2011 at 8:38 PM, cwillu <cwillu@gmail.com> wrote:
> It's by not-implemented-yet.=A0 Mount options are still currently glo=
bal to
> the filesystem.
Thanks for the info. I was testing combination of grub2, btrfs "/"
without separate /boot, and lzo. Using lzo feels much faster compared
to zlib, so right now I just use separate /boot/grub in ext4 to make
it work correctly.
--=20
=46ajar
>
> On May 8, 2011 7:35 AM, "Fajar A. Nugraha" <list@fajar.net> wrote:
>> Currently using Ubuntu Natty, kernel 2.6.38-9-generic, I have these
>> mount points using btrs subvolumes
>>
>> $ mount -t btrfs
>> /dev/sda2 on / type btrfs (rw,noatime,subvolid=3D256,compress-force=3D=
zlib)
>> /dev/sda2 on /home type btrfs (rw,noatime,subvolid=3D258,compress=3D=
lzo)
>>
>> Yet dmesg seems to show only zlib compression enabled
>> $ dmesg | grep btrfs
>> [ 11.097908] btrfs: force zlib compression
>>
>> Is this by design, or a bug?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-05-10 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 13:35 Compression: per filesystem, or per subvolume? Fajar A. Nugraha
2011-05-08 13:59 ` kehon
[not found] ` <BANLkTikS522HZBv+05md-okRey37aZd6gA@mail.gmail.com>
2011-05-10 9:51 ` Fajar A. Nugraha [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=BANLkTinDYX_twMsEDg0QgRrVmKKY_YDm+g@mail.gmail.com \
--to=list@fajar.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).