All autopkgtests for the newly accepted util-linux (2.33.1-0.1ubuntu3) for 
disco have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/240-6ubuntu5.3 (amd64, ppc64el)
openjdk-8/8u222-b10-1ubuntu1~19.04.1 (armhf, arm64, amd64, s390x, i386, ppc64el)

Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].


Thank you!

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.

  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Fix Committed
Status in util-linux package in Debian:

Bug description:
  fstrim weekly cronjob output in an unprivileged LXD container:

  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  The outcome is that it's purely an fstrim misbehaviour, it could be

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
   PATH=(custom, no user)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Test Case]
  * Ubuntu lxd container
  * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
  * fstrim will run and report errors "Operation not permitted" "Permission 
denied", ...

  Container shouldn't run fstrim, it should only be run at host level.

  [Potential Regression]

  None, the change will only block fstrim to be automatically run at
  scheduled time. One can still run fstrim on a container manually, even
  if there is no purpose of doing that.

  Xenial uses the cronjob approach /etc/cron.weekly/fstrim
  Bionic and late switched to a systemd timer.

  2 differents fixes (one for X, and one for B and late) will be needed,
  but they'll do same thing, which prevent fstrim to automatically run
  if inside a container both fixes using systemd-virt-detect.

  [Other Informations]

  * The systemd timer change upstream PR:

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to