On Mon, Mar 16, 2020 at 9:44 PM Chao Yu <yuch...@huawei.com> wrote: > > On 2020/3/16 17:52, John wrote: > > On Sun, Mar 15, 2020 at 9:24 PM Chao Yu <yuch...@huawei.com> wrote: > >> > >> What's your mount option and mkfs option on those two partitions, and > >> what's > >> your kernel version? > > > > I am mounting the partitions with systemd like so (/etc/fstab entry): > > LABEL=incoming /incoming f2fs noauto,x-systemd.automount 0 0 > > > > But I can reproduce this if I totally remove the entries within > > /etc/fstab, reboot, and mount manually like this: > > mount LABEL=incoming /incoming > > However, the directory where you trigger trim is "/mnt/media"? > > Quoted: > "Invoking it manually on the newer one gives this: > # fstrim -v /mnt/media > fstrim: /mnt/media: the discard operation is not supported" > > Could you give more details about that? What device is behind /mnt/media?
The SSD has two partitions on it formatted to F2FS. LABEL=incoming was created with f2fs-tools v1.12.0 LABEL=media was created with f2fs-tools v1.13.0 The physical device is a Samsung 860 EVO 2TB SSD. > > Inspecting my shell history, I created them both with this command: > > mkfs.f2fs -l incoming /dev/sdb2 > > > > I am running 5.5.9 on Arch Linux, but I believe I experienced this > > under previous 5.5.x series as well. > > > > If you create a F2FS partition using the latest stable release of > > f2fs-tools (1.13.0) are you able to reproduce the inability to trim? > > I can't, and also there is such option in mkfs to disable trim functionality > during format. > I might be misunderstanding. When you said "I can't" does that mean when you created a partition with f2fstools v1.13.0, mounted it, and then ran the fstrim on it, fstrim completed successfully? Which version of fstrim do you have installed? I am using util-linux 2.35.1. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
