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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
