https://bugzilla.kernel.org/show_bug.cgi?id=61601 János Tóth F. <janos666@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |janos666@xxxxxxxxxx --- Comment #18 from János Tóth F. <janos666@xxxxxxxxxx> --- I ran into this problem recently with kernel 4.5.5 when I tried copy-pasting all my mount options of / from fstab to the kernel cmdline as rootflags after I learned the space_cache=V2 mount option of Btrfs does not activate the new cache properly during the fstab-based RW remount of / when the kernel mounted it RO with default options including space_cache V1 (at least based on the kernel log messages but this should probably be investigated further if RO/RW has anything to do with this, or if it's enough to do the initial mount with this cache V2 option for a single time when the old space cache v1 should be invalidated and a new v2 type cache must be created or these have to stay for consecutive reboots). This might be Gentoo-specific but I also noticed localmount won't re-mount my / with the fstab options when I have this cache rootflag in my kernel cmdline. Thus, I have to manually re-mount / with noatime if I wish to have that option together with cache V2. I also realized this bug would pretty much be the only reason for me to keep a / entry in my fstab (to apply noatime). But more precisely, my current fstab entry is useless anyway (noatime isn't applied anyway when I specify RW and rootflags in the kernel cmdline). -- You are receiving this mail because: You are watching the assignee of the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
