Update of OS and LXD via snap cause: "Value too large for defined data type" when creating new files


We have been running LXC/LXD containers for several years now our servers.
Today after updating Ubuntu 22.04 LTS and upgrading LXD to 5.8 we are getting errors when processes create new files in our containers → “Value too large for defined data type”.

The containers are in “running” state.
Editing existing files like /var/log/syslog or /.bash_history have no problem.
However our own and other software is unable to start as it gets the “Value too large for defined data type” error while starting.

We have searched this forum and in other places, but nothing seems to be related to our situation.

Host details:
OS: Ubuntu 22.04.1 LTS
kernel: Linux five 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
storage: ZFS

Container details:
OS: Ubuntu 22.04.1 LTS

Example of errors in syslog of the container:

Nov 28 16:12:05 systemd[1]: systemd-logind.service: Failed to run 'start' task: Value too large for defined data type
Nov 28 16:12:05 systemd[1]: systemd-logind.service: Failed with result 'resources'.
Nov 28 16:12:05 systemd[1]: Failed to start User Login Management.
Nov 28 16:12:05 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5.

Container config:

architecture: x86_64
  image.architecture: x86_64
  image.description: Ubuntu 20.04 LTS server (20200428)
  image.os: ubuntu
  image.release: focal
  security.nesting: "true"
  volatile.base_image: 946e46f47f119ce400fab74f1d5d16fc9072e4185c8dd9034ed122651f87a834
  volatile.eth0.host_name: vethc50d4d55
  volatile.eth0.hwaddr: 00:16:3e:bd:e9:88
  volatile.idmap.base: "0"
  volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.last_state.idmap: '[]'
  volatile.last_state.power: RUNNING
  volatile.last_state.ready: "false"
  volatile.uuid: f8c70e2d-12a8-4651-ae27-3df001935e8a
devices: {}
ephemeral: false
- default
stateful: false
description: ""

Some information about the config:

  • the container was manually upgraded to 22.04
  • security.nesting: “true” was added to help resolve the issue mentioned above, but it did not.

Restarting the container is not helping. As we read in another post this might help in remapping the filesystem.

Reverting to LXD 5.7 also did not help.

Is this issue security related or what could be the cause?
Please let us know if more information is needed.

Thanks for any advice.

Its a shiftfs kernel bug, see How can I disable shiftfs on a lxd installed from source

1 Like

Thank you for the quick advice.