From: Calvin Walton <calvin.walton@kepstin.ca>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or newer?
Date: Wed, 23 Apr 2014 16:25:21 -0400 [thread overview]
Message-ID: <1398284721.20580.7.camel@sasami> (raw)
In-Reply-To: <vifl2b-87g.ln1@hurikhan77.spdns.de>
On Wed, 2014-04-23 at 21:06 +0200, Kai Krakow wrote:
> Пламен Петров <plamen@petrovi.no-ip.info> schrieb:
>
> I'm going with the module suggestion from Marc, too.
>
> > /dev/sda2 / btrfs relatime,compress=zlib 0 0
>
> This line looks kinda useless to me. The compress=zlib option won't be
> applied at boot and cannot be changed at runtime because AFAIR btrfs does
> not allow that yet.
... My understanding is that the compress= option on btrfs *can* be
changed at run time. After remounting with a compress= option, later
writes will be done using the newly selected algorithm.
The compress= option is filesystem-wide, you cannot currently use
different compress= options for different subvolumes. Mounting a
subvolume with a different compress= option will change the compression
algorithm for all mounted subvolumes on that filesystem.
(Note that I wouldn't recommend zlib on most systems as a / filesystem -
it's slow to decompress compared to lzo, so it will cause slower boots
if your disk is reasonably fast.)
--
Calvin Walton <calvin.walton@kepstin.ca>
next prev parent reply other threads:[~2014-04-23 20:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
2014-04-23 18:54 ` Marc MERLIN
2014-04-23 19:02 ` Hugo Mills
2014-04-23 19:06 ` Пламен Петров
2014-04-23 19:15 ` Marc MERLIN
2014-04-23 19:37 ` Пламен Петров
2014-04-23 20:58 ` Marc MERLIN
2014-04-23 21:54 ` Пламен Петров
2014-04-23 22:03 ` Marc MERLIN
2014-04-23 22:20 ` Пламен Петров
2014-04-23 22:40 ` Chris Murphy
2014-04-23 22:43 ` Hugo Mills
2014-04-23 22:50 ` Marc MERLIN
2014-04-23 22:53 ` Hugo Mills
2014-04-23 22:41 ` Hugo Mills
2014-04-24 12:34 ` Chris Mason
2014-04-24 12:36 ` Chris Mason
2014-04-24 17:08 ` Пламен Петров
2014-04-24 17:19 ` Пламен Петров
2014-04-24 17:33 ` Marc MERLIN
2014-04-24 17:44 ` Пламен Петров
2014-04-24 18:51 ` Пламен Петров
2014-04-24 19:31 ` Marc MERLIN
2014-04-24 20:26 ` Пламен Петров
2014-04-24 21:47 ` Chris Murphy
2014-04-24 21:06 ` Chris Murphy
2014-04-24 21:23 ` Пламен Петров
[not found] ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>
2014-04-24 23:07 ` Marc MERLIN
2014-04-25 0:04 ` Chris Murphy
2014-04-25 0:08 ` Chris Mason
2014-04-25 5:04 ` Пламен Петров
2014-04-25 7:02 ` Duncan
2014-04-25 5:03 ` Пламен Петров
2014-04-23 19:06 ` Kai Krakow
2014-04-23 20:25 ` Calvin Walton [this message]
2014-04-23 22:34 ` Chris Murphy
2014-04-24 3:23 ` Chris Murphy
2014-04-24 6:27 ` Fajar A. Nugraha
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=1398284721.20580.7.camel@sasami \
--to=calvin.walton@kepstin.ca \
--cc=hurikhan77+btrfs@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 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.