From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: /etc/fstab rootfs options vs grub2 rootflags cmdline
Date: Wed, 4 May 2016 15:54:15 +0000 (UTC) [thread overview]
Message-ID: <pan$6ee8b$a34d8ed2$894ceb38$41a8085e@cox.net> (raw)
In-Reply-To: f8233c24-e336-4d31-a4cb-f3b0f97d1305@linuxsystems.it
Niccolò Belli posted on Wed, 04 May 2016 15:52:39 +0200 as excerpted:
> Thanks,
> Now my fstab option are
> rw,noatime,compress=lzo,discard,autodefrag,subvolid=257,subvol=/@
> I tried to add rootflags=noatime,compress=lzo,discard,autodefrag to
> GRUB_CMDLINE_LINUX in /etc/default/grub as you suggested but my system
> didn't manage to boot, probably because grub automatically adds
> rootflags=subvol=@ and only a single rootflags can be taken into
> account.
> Do you have any suggestion?
What about the subvol=/@?
I think if you specifically add your own rootflags, grub won't add its
own, and you said
noatime,compress=lzo,discard,autodefrag
but left off the subvol=/@ (unless you simply forgot to put it in the
posting), and without that, it would have mounted the btrfs default
subvolume, which would be (the filesystem's) / (subvolid=5) if you
haven't changed it, and would have failed to boot as a result.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-04 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 9:46 /etc/fstab rootfs options vs grub2 rootflags cmdline Niccolò Belli
2016-05-04 11:40 ` Duncan
2016-05-04 13:52 ` Niccolò Belli
2016-05-04 15:54 ` Duncan [this message]
2016-05-04 16:31 ` Andrei Borzenkov
2016-05-04 18:07 ` Chris Murphy
2016-05-04 18:34 ` Duncan
2016-05-04 19:28 ` Chris Murphy
2016-05-04 18:56 ` Austin S. Hemmelgarn
2016-05-04 17:58 ` Chris Murphy
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='pan$6ee8b$a34d8ed2$894ceb38$41a8085e@cox.net' \
--to=1i5t5.duncan@cox.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).