Ubuntu
e2fsprogs package

e2scrub shouldn't run in a container

Bug #1939305 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
New
Undecided
Unassigned

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.

See original description
Jamie Strandboge (jdstrand)
description: updated
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.