Hello,

On 2020/3/15 2:09, John wrote:
> Running `fstrim -a -v` is not detecting my f2fs partition that I
> created just a few days ago but it does detect an older f2fs partition
> and trims it as expected.  Both partitions are on the same SSD.  The
> older partition is FSVER=1.12 whereas the newer one is FSVER=1.13
> (reported by `lsblk -f`).

What's your mount option and mkfs option on those two partitions, and what's
your kernel version?

I checked the code, only place where we give 'not supported' is as below
by checking whether underlying device supports discard.

f2fs_ioc_fitrim()

        if (!f2fs_hw_support_discard(F2FS_SB(sb)))
                return -EOPNOTSUPP;

So this should not happen that two partitions locates in one device have
inconsistent discard support status.

Thanks,

> 
> Invoking it manually on the newer one gives this:
> # fstrim -v /mnt/media
> fstrim: /mnt/media: the discard operation is not supported
> 
> And invoking it manually on the older one gives this:
> # fstrim -v /incoming
> /mnt/incoming:  1.7 GiB (1762152448 bytes) trimmed on /dev/sda2
> 
> Thanks.
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> .
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to