From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Chris Murphy <chris@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: remount and conflicting ssd options?
Date: Sat, 15 Apr 2017 20:20:07 +0200 [thread overview]
Message-ID: <4096c717-4804-bce4-d7da-de962218f190@mendix.com> (raw)
In-Reply-To: <CAJCQCtTU6M1c-B1thYtTBidyEpM9AWPMSPU=NGxj3QHnqTM7+A@mail.gmail.com>
On 04/15/2017 08:17 PM, Chris Murphy wrote:
> I don't understand this:
>
> /dev/mmcblk0p3 on / type btrfs
> (rw,noatime,seclabel,compress=zlib,nossd,ssd_spread,space_cache,commit=150,subvolid=260,subvol=/root)
>
>
> The fstab uses ssd_spread. It looks like during startup the initial
> option is ssd via autodetection and then at switchroot time, when it
> goes ro to rw, the fstab options are applied and it becomes
> ssd_spread. Fine.
>
> Then later I tried
>
> mount -o remount,ssd
>
> To go back to regular ssd option, but nothing happens, mount still
> shows ssd_spread. And then if I do
>
> mount -o remount,nossd
>
> I get the above mount output with nossd,ssd_spread options which would
> seem to be a contradiction. At least it's confusing. So... now what?
>
> kernel 4.10.8-200.fc25.x86_64
>
See thread "Cosmetics bug: remounting ssd does not clear nossd", started
on Mar 31. It has all the answers. :-)
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-04-15 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 18:17 remount and conflicting ssd options? Chris Murphy
2017-04-15 18:20 ` Hans van Kranenburg [this message]
2017-04-15 18:31 ` Adam Borowski
2017-04-15 18:41 ` Chris Murphy
2017-04-15 18:50 ` Adam Borowski
2017-04-15 20:35 ` Chris Murphy
2017-04-16 0:41 ` Hans van Kranenburg
2017-04-16 18:03 ` Chris Murphy
2017-04-15 18:57 ` Hans van Kranenburg
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=4096c717-4804-bce4-d7da-de962218f190@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=chris@colorremedies.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;
as well as URLs for NNTP newsgroup(s).