linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: <linux-btrfs@vger.kernel.org>
Subject: /etc/fstab rootfs options vs grub2 rootflags cmdline
Date: Wed, 04 May 2016 11:46:10 +0200	[thread overview]
Message-ID: <79249c4d-eab0-43fa-a6ae-b670699891dc@linuxsystems.it> (raw)

Hi,
I have the following options for my rootfs in /etc/fstab:
rw,relatime,compress=lzo,ssd,discard,space_cache,autodefrag,subvolid=257,subvol=/@

grub2 already placed rootflags=subvol=@ in its cmdline, but not the other 
options. I suppose that some of them will automatically be set during 
remount, but I'm not sure if all of them will.

Do you know which ones should I manually add to GRUB_CMDLINE_LINUX in 
/etc/default/grub?

Is there any way to check to if they are already enabled?
mount shows /dev/mapper/cryptroot on / type btrfs 
(rw,relatime,compress=lzo,ssd,discard,space_cache,autodefrag,subvolid=257,subvol=/@) 
but I'm not sure if I can trust it: I read that space_cache should trigger 
"enabling free space tree" in dmesg but I can't see it and I don't know 
about the others.

Thanks,
Niccolò

             reply	other threads:[~2016-05-04  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04  9:46 Niccolò Belli [this message]
2016-05-04 11:40 ` /etc/fstab rootfs options vs grub2 rootflags cmdline Duncan
2016-05-04 13:52   ` Niccolò Belli
2016-05-04 15:54     ` Duncan
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=79249c4d-eab0-43fa-a6ae-b670699891dc@linuxsystems.it \
    --to=darkbasic@linuxsystems.it \
    --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).