On 5/7/25 3:28 PM, Jaegeuk Kim wrote: >> But as far as I can tell, at least for the extent cache, remount is handled >> properly already (with the hunk above): >> >> # mkfs/mkfs.f2fs -c /dev/v...@vdc.file /dev/vdb >> # mount /dev/vdb mnt >> # mount -o remount,noextent_cache mnt >> mount: /root/mnt: mount point not mounted or bad option. >> dmesg(1) may have more information after failed mount system call. >> # dmesg | tail -n 1 >> [60012.364941] F2FS-fs (vdb): device aliasing requires extent cache >> # >> >> I haven't tested with i.e. blkzoned devices though, is there a testcase >> that fails for you? > I'm worrying about any missing case to check options enabled by > default_options. > For example, in the case of device_aliasing, we rely on enabling extent_cache > by default_options, which was not caught by f2fs_check_opt_consistency. > > I was thinking that we'd need a post sanity check.
I see. If you want a "belt and suspenders" approach and it works for you, no argument from me :) -Eric _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
