You are not logged in.

#1 2020-03-11 23:11:14

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

I am confused why running # fstrim -a -v is not detecting my f2fs partition that I created just a few days ago.  Querying lsblk, it shows up as FSVER 1.13 ... I have an older F2FS partition that shows up as FSVER 1.12 and that partition is picked-up by fstrim so I am wondering what changed with respect to this between these versions.

Invoking it manually gives this:

# fstrim -v /mnt/media             
fstrim: /mnt/media: the discard operation is not supported

And for reference:

% mount | grep '/mnt/media' 
/dev/mapper/media-crypt on /mnt/media type f2fs (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix)

EDIT: Note that I edited the original thread removing some info to make it more clear.

Last edited by graysky (2020-03-12 20:21:38)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2020-03-12 01:07:01

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

Yes, it should work with crypto LUKS https://www.kernel.org/doc/html/latest/ … w_discards

But, your underlying medium must support it too.

F.I. https://en.wikipedia.org/wiki/Trim_(computing)#SD/MMC

Offline

#3 2020-03-12 19:59:43

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

@qinohe - Thanks for the link, I too thought it should be supported.  The hardware is a Samsung 860 EVO.  I haven't seen one yet that didn't support discard so I am at a loss as to why fstrim does not hit it.

EDIT: note that I edited the original title and post to more accurately reflect my situation.

Last edited by graysky (2020-03-12 20:15:17)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#4 2020-03-12 20:24:38

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

I have a few then:

• Is your drive an external one; won't work, you can't enable trim on external drives(far as I know)
• You know about security implications performing encryption on non rotating disks?
• You know trim is in rare cases able to f**k your drive?
• Is your drive a drive with high loads to it? If not, don't enable trim it really isn't necessary especially on these new drives like 860 evo

Of course in the end it all boils down to your own judgment and how 'you' look at the case, but anyway the above may provide some rationales to consider;)

Offline

#5 2020-03-12 23:20:32

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

In reflection to your changed title, I'm not a f2fs user myself so I hand you the links, may provide some clues to you...
You may already have them but anyway here you go;)

https://git.archlinux.org/svntogit/pack … f2fs-tools

https://git.kernel.org/pub/scm/linux/ke … s.git/log/

Offline

#6 2020-03-13 21:54:04

newbie1962
Member
From: italy
Registered: 2012-07-24
Posts: 137

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

Apparently my poor ssd, external: Intenso Portable SSD (scsi)
it does.

arch% lsblk 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   477G  0 disk 
├─sda1   8:1    0   954M  0 part 
├─sda2   8:2    0  19,5G  0 part 
├─sda3   8:3    0  1000M  0 part /boot
└─sda4   8:4    0    21G  0 part /
sdb      8:16   0 698,7G  0 disk 
├─sdb1   8:17   0   400M  0 part 
├─sdb2   8:18   0   260M  0 part 
├─sdb3   8:19   0   128M  0 part 
├─sdb4   8:20   0 606,6G  0 part 
├─sdb5   8:21   0    72G  0 part 
├─sdb6   8:22   0   923M  0 part 
├─sdb7   8:23   0   486M  0 part 
├─sdb8   8:24   0   450M  0 part 
└─sdb9   8:25   0  17,5G  0 part 
sr0     11:0    1  1024M  0 rom  
archl%  sudo parted -l
[sudo] password di eroe: 
Modello: Intenso Portable SSD (scsi)
Disco /dev/sda: 512GB
Dimensione del settore (logica/fisica): 512B/4096B
Tabella delle partizioni: gpt
Flag del disco: 

Numero  Inizio  Fine    Dimensione  File system  Nome  Flag
 1      1049kB  1001MB  1000MB      fat32              avvio, esp
 2      1001MB  21,9GB  20,9GB      ext4
 3      21,9GB  23,0GB  1049MB      fat32              avvio, esp
 4      23,0GB  45,5GB  22,5GB      ext4
arch% 

Trim ssd portable intenso

arch% sudo fstrim -v /
/: 6,4 GiB (6828621824 bytes) trimmed
arch% 

While the old portable samsung mm1 now burnt, after exactly 3 years, it was not running, I think it is a flaw of the samsung portable ssd.
Cheers

Last edited by newbie1962 (2020-03-14 16:06:14)


hp-envy dv7

Offline

#7 2020-03-13 21:56:08

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

@newbie1962 - Can you post the output from lsblk -f


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#8 2020-03-14 16:04:46

newbie1962
Member
From: italy
Registered: 2012-07-24
Posts: 137

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

arch% lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                         
├─sda1
│    ntfs         WINRE 6C601F52601F227E                                    
├─sda2
│    vfat   FAT32       F46A-0B46                                           
├─sda3
│                                                                           
├─sda4
│    ntfs         Windows 8.1
│                       7A646DD0646D9025                                    
├─sda5
│    ntfs         Windows10
│                       5880C14C80C130F4                                    
├─sda6
│    ntfs               7EC86182C8613A13                                    
├─sda7
│    ntfs               8CF45F2DF45F18B2                                    
├─sda8
│    ntfs               E81033BF10339412                                    
└─sda9
     ntfs         RECOVERY
                        00761CEF761CE6E6                                    
sdb                                                                         
├─sdb1
│    vfat   FAT32       242D-BD38                                           
├─sdb2
│    ext4   1.0   arch don
│                       626e6897-c99e-496a-adc2-324b16b1084a                
├─sdb3
│    vfat   FAT32       B14E-90FF                             946,8M     5% /boot
└─sdb4
     ext4   1.0   arch eroe
                        6dff60ac-94c7-4c75-b416-e727cbda9b47    5,2G    70% /
sr0                                                                         
arch% 

hp-envy dv7

Offline

#9 2020-03-14 17:57:34

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: Seems fstrim does not recognize FSVER 1.13 of F2FS partitions

@newbie - None of your partitions are formatted to f2fs.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

Board footer

Powered by FluxBB