Hi
On Tue, Jun 08, 2021 at 11:43:06PM +0200, Laurent Bigonville wrote:
> Well I would expect that if I'm running fstrim, the same blocks would not be
> trimmed again (even after reboot) if I'm running the command again
But how would it know that it was already trimmed?
> Here it seems that it's
Le 8/06/21 à 21:24, Bastian Blank a écrit :
Hi
Hello,
On Tue, Jun 08, 2021 at 03:48:11PM +0200, Laurent Bigonville wrote:
There is definitely something boggus here
Yes, just tested it now and it's still happening with the kernel currently
in unstable (5.10.40-1)
Why do you think this
Hi
On Tue, Jun 08, 2021 at 03:48:11PM +0200, Laurent Bigonville wrote:
> > > There is definitely something boggus here
> Yes, just tested it now and it's still happening with the kernel currently
> in unstable (5.10.40-1)
Why do you think this numbers are wrong? "fstrim" initially requests
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
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
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
6 matches
Mail list logo
