Skip to content

system journal spam: err="Failed to stat tmpfs:: no such file or directory" #2904

@xorbug

Description

@xorbug

Is there an existing issue for this?

  • There is no existing issue for this bug

Is this happening on an up to date version of Incus?

  • This is happening on a supported version of Incus

Incus system details

driver: qemu | lxc                                       
  driver_version: 10.2.0 | 6.0.5
  firewall: nftables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    idmapped_mounts: "true"
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    uevent_injection: "true"
    unpriv_binfmt: "false"
    unpriv_fscaps: "true"
  kernel_version: 6.1.0-42-amd64
  lxc_features:
    cgroup2: "true"
    core_scheduling: "true"
    devpts_fd: "true"
    idmapped_mounts_v2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Debian GNU/Linux
  os_version: "12"
  project: default
  server: incus
  server_clustered: false
  server_event_mode: full-mesh
  server_pid: 1813473
  server_version: "6.21"
  storage: btrfs
  storage_version: "6.2"
  storage_supported_drivers:
  - name: dir
    version: "1"
    remote: false
  - name: btrfs
    version: "6.2"
    remote: false
  - name: lvm
    version: 2.03.16(2) (2022-05-18) / 1.02.185 (2022-05-18) / 4.47.0
    remote: false
  - name: truenas
    version: 0.7.3
    remote: true

Instance details

Instance has a tmpfs disk device:

devices:
  something:
    path: /path/to/something
    size: 10GiB
    source: 'tmpfs:'
    type: disk

Instance log

No response

Current behavior

System journal get spammed with this line every 15 seconds:

level=warning msg="Failed to get fs stats" err="Failed to stat tmpfs:: no such file or directory" instance=name instanceType=container project=default

Inside the instance, the tmpfs device is reported as correctly mounted at the specified path.

Expected behavior

Don't spam logs if everything is ok.

Steps to reproduce

  1. Add a tmpfs device to an instance
  2. Start the instance
  3. Inspect system journal

Metadata

Metadata

Assignees

No one assigned

    Labels

    IncompleteWaiting on more information from reporter

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions