Bug#909473: fstrim shows incorrect trimmed size after reboot

From	Laurent Bigonville <bigon@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#909473: fstrim shows incorrect trimmed size after reboot
Date	2021-06-08 16:00 +0200
Message-ID	<CnKqS-1Sy-5@gated-at.bofh.it> (permalink)
References	<wBxnA-5dG-1@gated-at.bofh.it> <CjQuR-7w-1@gated-at.bofh.it> <wBxnA-5dG-1@gated-at.bofh.it> <CjQuR-7w-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Control: tags -1 - moreinfo

Le 28/05/21 à 21:28, Salvatore Bonaccorso a écrit :
> Control: tags -1 + moreinfo
>
> Hi Laurent,
>
> On Mon, Sep 24, 2018 at 01:37:01PM +0200, Laurent Bigonville wrote:
>> Package: src:linux
>> Version: 4.18.8-1
>> Severity: normal
>>
>> Hi,
>>
>> Not sure who to blame here, but when running fstrim -va it show the size
>> of the disk it has trimmed, if I'm running fstrim again it shows 0 for
>> all the disk.
>>
>> If I reboot, and then run fstrim again it shows (almost) the same value
>> as the 1st time. All the disks have the discard option enabled, all fs
>> are ext4, except /boot which is ext2/
>>
>> See the logs:
>>
>> bigon@valinor:~$ journalctl -u fstrim.service
>> -- Logs begin at Sat 2018-09-08 12:48:02 CEST, end at Mon 2018-09-24 13:32:05 CEST. --
>> sep 17 10:44:21 valinor systemd[1]: Starting Discard unused blocks...
>> sep 17 10:44:51 valinor fstrim[11186]: /var/cache/apt-cacher-ng : 930,1 MiB (975245312 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /var/lib/sbuild/build : 9,8 GiB (10463989760 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /var/lib/docker : 10 GiB (10713788416 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /home : 11,3 GiB (12105969664 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: /boot : 126,9 MiB (133014528 octets) taillés
>> sep 17 10:44:51 valinor fstrim[11186]: / : 8,6 GiB (9217847296 octets) taillés
>> sep 17 10:44:51 valinor systemd[1]: Started Discard unused blocks.
>> -- Reboot --
>> sep 24 10:12:35 valinor systemd[1]: Starting Discard unused blocks...
>> sep 24 10:13:08 valinor fstrim[26936]: /var/lib/sbuild/build : 9,8 GiB (10455736320 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /var/cache/apt-cacher-ng : 922,8 MiB (967565312 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /var/lib/docker : 11,4 GiB (12180299776 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /home : 11 GiB (11825807360 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: /boot : 126,9 MiB (133008384 octets) taillés
>> sep 24 10:13:08 valinor fstrim[26936]: / : 8,6 GiB (9219850240 octets) taillés
>> sep 24 10:13:08 valinor systemd[1]: Started Discard unused blocks.
>> -- Reboot --
>> sep 24 13:20:54 valinor systemd[1]: Starting Discard unused blocks...
>> sep 24 13:21:28 valinor fstrim[6751]: /var/lib/docker : 11,4 GiB (12181008384 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /var/cache/apt-cacher-ng : 793,9 MiB (832487424 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /home : 10,8 GiB (11617431552 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /var/lib/sbuild/build : 9,8 GiB (10463989760 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: /boot : 126,9 MiB (133008384 octets) taillés
>> sep 24 13:21:28 valinor fstrim[6751]: / : 8,6 GiB (9211752448 octets) taillés
>> sep 24 13:21:28 valinor systemd[1]: Started Discard unused blocks.
>> sep 24 13:32:05 valinor systemd[1]: Starting Discard unused blocks...
>> sep 24 13:32:05 valinor fstrim[7323]: /var/lib/docker : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /var/cache/apt-cacher-ng : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /var/lib/libvirt : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /home : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /var/lib/sbuild/build : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /var/lib/flatpak : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: /boot : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor fstrim[7323]: / : 0 B (0 octets) taillés
>> sep 24 13:32:05 valinor systemd[1]: Started Discard unused blocks.
>>
>> There is definitely something boggus here
> Is this still something you are able to reproduce this way with a
> recent kernel?

Hello Salvatore,

Yes, just tested it now and  it's still happening with the kernel 
currently in unstable (5.10.40-1)

Thread

Bug#909473: fstrim shows incorrect trimmed size after reboot Salvatore Bonaccorso <carnil@debian.org> - 2021-05-28 21:40 +0200
  Processed: Re: Bug#909473: fstrim shows incorrect trimmed size  after reboot "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-28 21:40 +0200
  Bug#909473: fstrim shows incorrect trimmed size after reboot Laurent Bigonville <bigon@debian.org> - 2021-06-08 16:00 +0200
    Processed: Re: Bug#909473: fstrim shows incorrect trimmed size  after reboot "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-06-08 16:00 +0200
    Bug#909473: fstrim shows incorrect trimmed size after reboot Bastian Blank <waldi@debian.org> - 2021-06-08 21:50 +0200
      Bug#909473: fstrim shows incorrect trimmed size after reboot Laurent Bigonville <bigon@debian.org> - 2021-06-08 23:50 +0200
        Bug#909473: fstrim shows incorrect trimmed size after reboot Bastian Blank <waldi@debian.org> - 2021-06-09 00:00 +0200

csiph-web