Hello Jamie, thanks for reporting the issue. Do you plan to send a patch upstream?
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/scrub/e2scrub_all.timer.in?id=a2df58945c232186c96ffa8958f555ed33965ff7 has the relevant addressees. Best regards Heinrich -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939305 Title: e2scrub shouldn't run in a container Status in e2fsprogs package in Ubuntu: New Bug description: This bug is similar to https://bugs.launchpad.net/ubuntu/+source/util- linux/+bug/1589289 (fstrim), but for the e2fsprogs timer e2scrub_all.timer. IME, the container itself shouldn't be running 'ext4 Metadata Checks for All Filesystems...' and that should be left up to the host to handle. I noticed this in a 20.04 container. I suspect the fix is similar to fstrim and to simply add 'ConditionVirtualization=!container' to the systemd timer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
