If I run the trim command consecutively, each time it tells me it managed to trim again, such as below.  The amount trimmed just happens to be the total free space not he drives.  (First Example)

 

On other systems, such as Ubuntu, the trim command will report back how much data was trimmed, not the total of the drive, with consecutive runs coming back with zero because obviously it's just been trimmed and doesn't need to be done again. (Second Example)

 

Both examples are copy / paste from real systems

 

Example 1 - Unraid

root@Tower:/mnt/user# fstrim -av

/etc/libvirt: 920.7 MiB (965427200 bytes) trimmed

/var/lib/docker: 10.8 GiB (11525165056 bytes) trimmed

/mnt/disks/SAMSUNG_MZ7KM960HAHP-00005_S2HTNYAG700753: 822.4 GiB (883001917440 bytes) trimmed

/mnt/cache: 929.6 GiB (998104616960 bytes) trimmed

root@Tower:/mnt/user# fstrim -av

/etc/libvirt: 920.7 MiB (965427200 bytes) trimmed

/var/lib/docker: 10.8 GiB (11524747264 bytes) trimmed

/mnt/disks/SAMSUNG_MZ7KM960HAHP-00005_S2HTNYAG700753: 822.4 GiB (883000401920 bytes) trimmed

/mnt/cache: 929.6 GiB (998104616960 bytes) trimmed

root@Tower:/mnt/user#

 

Example 2 - Ubuntu 18

root@UBUMED01:/home/xxxj# fstrim -av

/: 22.4 GiB (24069234688 bytes) trimmed

root@UBUMED01:/home/xxxj# fstrim -av

/: 0 B (0 bytes) trimmed

root@UBUMED01:/home/xxxj#

 

Can anyone else replicate this?  I do have the trim plugin installed - but actually am wondering if it needs to be, perhaps it's conflicting with the native trim?  Surely that would have been worked out - though I did see this situation with pre-clear - totally unnecessary for most people IMO.

 

Thanks (I'm an UNRAID Noob, just not an IT Noob).

I can replicate this.  I don't have the trim plugin installed

 

On my Unraid server

root@server:~# fstrim -av 
/etc/libvirt: 921 MiB (965681152 bytes) trimmed
/var/lib/docker: 4.8 GiB (5113901056 bytes) trimmed
/mnt/disks/virtualisation: 113.2 GiB (121517445120 bytes) trimmed
root@server:~# fstrim -av 
/etc/libvirt: 921 MiB (965681152 bytes) trimmed
/var/lib/docker: 4.8 GiB (5100285952 bytes) trimmed
/mnt/disks/virtualisation: 113.2 GiB (121517670400 bytes) trimmed

On my Solus laptop

chbmb@thinkpad ~ $ sudo fstrim -av
Password: 
/home: 197.3 GiB (211824361472 bytes) trimmed on /dev/sda1
/: 98.5 GiB (105773998080 bytes) trimmed on /dev/sdb3
chbmb@thinkpad ~ $ sudo fstrim -av
/home: 0 B (0 bytes) trimmed on /dev/sda1
/: 0 B (0 bytes) trimmed on /dev/sdb3

Edited January 23, 20197 yr by CHBMB

Different versions of fstrim?

# fstrim -V
fstrim from util-linux 2.33

 

fstrim from util-linux 2.32 on mine. Someone running the release candidate?


Sent from my iPhone using Tapatalk

Version 2.33 is included in 6.7.0-rc1

 

What does Ununtu use?

Edited January 23, 20197 yr by bonienl

Solus is using 2.33
 

chbmb@thinkpad ~ $ fstrim -V
fstrim from util-linux 2.33

 

The Ubuntu I tested it on is using 2.31.1


Sent from my iPhone using Tapatalk

This is from v6.7.0rc1 @bonienl

root@matrix:~# fstrim -av
/var/lib/docker: 882.4 MiB (925265920 bytes) trimmed on /dev/loop2
root@matrix:~# fstrim -av
/var/lib/docker: 882.4 MiB (925265920 bytes) trimmed on /dev/loop2
root@matrix:~# fstrim -V
fstrim from util-linux 2.33

 

Hmmm so same problem there then. I wonder if it’s actually trimming anything or just reporting it wrong. I do recall there was a way to find out.


Sent from my iPhone using Tapatalk

This is from the fstrim documentation:

 

fstrim will report the same potential discard bytes each time, but only sectors which had been written to between the discards would actually be discarded by the storage device.

 

In other words it is normal to see the same value again when the trim action is repeated.

Or it is normal on some versions and not normal on others at least. Which makes me suspicious!


Sent from my iPhone using Tapatalk