Your message dated Wed, 28 Sep 2016 19:43:43 +0200
with message-id <[email protected]>
and subject line Re: fstrim doesn't work on ntfs
has caused the Debian Bug report #839069,
regarding fstrim doesn't work on ntfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
839069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839069
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntfs-3g
Version: 1:2016.2.22AR.1-3
My setup is as follows:
# cat /etc/fstab | grep -i ntfs
/dev/sda2 /media/my_data ntfs-3g
rw,user,noatime,discard,commit=300 0 0
# aptitude show util-linux | grep Version
Version: 2.28.1-1
# aptitude show ntfs-3g | grep Version
Version: 1:2016.2.22AR.1-3
# uname -a
Linux my_host_name 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18)
x86_64 GNU/Linux
# dmesg| grep "ATA.*SSD"
[ 2.111271] ata1.00: ATA-8: SAMSUNG SSD PM830 2.5" 7mm 512GB,
CXM03D1Q, max UDMA/133
[ 2.124231] scsi 0:0:0:0: Direct-Access ATA SAMSUNG SSD PM83
3D1Q PQ: 0 ANSI: 5
Now:
# mount /media/my_data/
# ls /media/my_data/
my_private_directory $RECYCLE.BIN System Volume Information
Windows10Upgrade
# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
Given that the current version of the ntfs-3g driver supports trimming,
and given that fstrim ran twice, I expect that the second command
reports "0 B (0 bytes) trimmed", contrary to the above.
Changing ntfs-3g to ntfs in /etc/fstab has no influence.
--- End Message ---
--- Begin Message ---
On 09/28/2016 07:40 PM, Jean-Pierre André wrote:
# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
Given that the current version of the ntfs-3g driver
supports trimming, and given that fstrim ran twice, I
expect that the second command reports "0 B (0 bytes)
trimmed", contrary to the above.
This does not mean fstrim not to work, it means the
trimming was done twice. ntfs-3g does not keep track
of the clusters which were not written since the last
trimming and all unused clusters are trimmed.
Note that the fstrim manual states "By default, fstrim
will discard all unused blocks in the filesystem."
I see. Thanks! Closing.
--- End Message ---
