[Bug 1939305] [NEW] e2scrub shouldn't run in a container

[Jamie Strandboge]

Public bug reported:

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.

** Affects: e2fsprogs (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source/util-
- linux/+bug/1589289 (fstrim), but for the e2fsprogs timers:
- e2scrub at .service and 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.
+ 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 timers.
+ 'ConditionVirtualization=!container' to the systemd timer.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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