To be honest, I'd rather this was addressed upstream with a suitable modification of the "zpool trim" command; either by ignoring this case by default (I believe this was the behavior in ZoL <2.0) or by adding a "--quiet" flag or similar.
'zpool status -t pool' does report whether TRIM is supported for each vdev, but the effort of parsing that in the cron script seems excessive. Grepping out that specific error message would probably be okay as an interim workaround. Colm On Thu, 11 Feb 2021 at 10:03, Petter Reinholdtsen <p...@hungry.com> wrote: > [Christoph Biedl] > > Please find a solution for this - preferably by checking beforehand > > whether trimming is possible. Or if all else fails, by muting stderr > > from the "zpool trim" command. Although that might hide serious errors > > as well. > > Good point. This can fill up the disk on a server where no-one check > the email. > > Any idea how to figure out if trimming is possible/useful? > > -- > Happy hacking > Petter Reinholdtsen > > _______________________________________________ > Pkg-zfsonlinux-devel mailing list > pkg-zfsonlinux-de...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-zfsonlinux-devel -- Colm Buckley | c...@tuatha.org
