discard=async triggers continuous disc activity for me without any calls to the filesystem. Is this intentional? On Mon, Jun 22, 2020 at 5:57 PM Chris Mason <clm@xxxxxx> wrote: > > On 22 Jun 2020, at 10:23, David Sterba wrote: > > > On Mon, Jun 22, 2020 at 04:02:34PM +0200, Ulli Horlacher wrote: > >> On Sun 2020-06-21 (18:57), Chris Murphy wrote: > >> > >>>>> You need to check fstrim.timer, which in turn triggers > >>>>> fstrim.service. > >>>> > >>>> root@fex:~# cat /lib/systemd/system/fstrim.timer > >>>> > >>>> root@fex:~# cat /lib/systemd/system/fstrim.service > >> > >>> I'm familiar with the contents of the files. Do you have a question? > >> > >> > >> You have deleted my question, it have asked: > >> > >> This means: an extra fstrim (via btrfsmaintenance script, etc) is > >> unnecessary? > > > > You need only one service, either from the fstrim or from > > btrfsmaintenance. > > Dennis’s async discard features are working much better here than > either periodic trims or the traditional mount -o discard. I’d > suggest moving to mount -o discard=async instead. > > -chris
