From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: 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 21:06:39 +0200 [thread overview]
Message-ID: <vifl2b-87g.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: 000001cf5f19$ac92b2b0$05b81810$@petrovi.no-ip.info
Пламен Петров <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.
This is because during initial mount by the kernel, /etc/fstab has not yet
been read (and cannot for obvious reasons). The only way around it is to
also append rootflags= to the kernel cmdline. This also explains why in a
few other cases btrfs cannot be mounted, although it should make no
difference in your case except the compress option won't be applied to the
running file system.
Also, you may want to try rootdelay=2 or something similar, it sometimes
help mounting btrfs at boot. But first try the suggestion abount baking the
btrfs module right into the kernel.
--
Replies to list only preferred.
next prev parent reply other threads:[~2014-04-23 19:19 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 [this message]
2014-04-23 20:25 ` Calvin Walton
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=vifl2b-87g.ln1@hurikhan77.spdns.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox