• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

‘lxc_cgfs – Device or resource busy – failed to set memory.use_hierarchy to 1; continuing’ – error while starting LXC container

by admin

The Problem

While starting lxc it gives the below error:

lxc-start 1491315722.354 ERROR lxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start 1491315722.354 ERROR lxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start 1497957841.930 ERROR lxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start 1497957841.937 ERROR lxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing

The Solution

Considering a scenario where we get the Error:Device or resource busy – failed to set memory.use_hierarchy to 1; continuing:

# lxc-start --name CentOS7
lxc-start: cgfs.c: handle_cgroup_settings: 2077 Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Detected virtualization 'lxc'.
Welcome to CentOS Linux Server 7.1!
Failed to insert module 'autofs4'
Set hostname to [CentOS7].
[ OK ] Reached target Remote File Systems.
[ OK ] Created slice Root Slice.
[ OK ] Created slice User and Session Slice.
[ OK ] Created slice System Slice.
[ OK ] Reached target Slices.
[ OK ] Created slice system-getty.slice.

The parameter /cgroup/memory/memory.use_hierarchy is set to 0 causing the issue. Use the below command to check the current value of the parameter.

# cat /proc/mounts | grep -i mem
cgroup /cgroup/memory cgroup rw,relatime,memory 0 0

# ls /cgroup/memory/memory.use_hierarchy
/cgroup/memory/memory.use_hierarchy

# cat /cgroup/memory/memory.use_hierarchy
0

If we try to set the value to 1 it still throws the same error:

# echo 1 > /cgroup/memory/memory.use_hierarchy
-bash: echo: write error: Device or resource busy

In order to get rid of the Error : Device or resource busy – failed to set memory.use_hierarchy to 1; continuing we need to follow the below steps:

  1. Stop the container
  2. Stop cgconfig service
  3. Start cgconfig service
  4. Set the parameter /cgroup/memory/memory.use_hierarchy to 1
  5. Start the container
# lxc-stop --name CentOS7
# /etc/init.d/cgconfig stop
Stopping cgconfig service: [ OK ]
# cat /proc/mounts | grep -i mem
#
# /etc/init.d/cgconfig start
Starting cgconfig service: [ OK ]
# cat /cgroup/memory/memory.use_hierarchy
0
# echo 1 > /cgroup/memory/memory.use_hierarchy
# cat /cgroup/memory/memory.use_hierarchy
1
# lxc-start --name CentOS7
systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Detected virtualization 'lxc'.

Welcome to CentOS Server 7.1!

Failed to insert module 'autofs4'
Set hostname to .
[ OK ] Reached target Remote File Systems.
[ OK ] Created slice Root Slice.

Filed Under: CentOS/RHEL 6, CentOS/RHEL 7, Linux

Some more articles you might also be interested in …

  1. How to Configure SSH to restrict Users/Groups with allow and deny directives
  2. ASMLib-Managed Disks on Multipathed iSCSI Targets are not Discovered after Server Reboot in CentOS/RHEL 7
  3. How to Stop SSH Session From Getting Timed Out
  4. CentOS/RHEL 8: “ACPI MEMORY OR I/O RESET_REG” Server Hung after reboot
  5. Sample /etc/mke2fs.conf file
  6. How to Troubleshoot Performance Issues on Linux – Beginners Guide
  7. lscpu Command Examples in Linux
  8. ifrename: command not found
  9. CentOS / RHEL : How to Install and Configure OpenSSH Server and Client
  10. Understanding rsyslog Filter Options

You May Also Like

Primary Sidebar

Recent Posts

  • qemu-system-x86_64: command not found
  • timedatectl: command not found
  • mpirun.openmpi: command not found
  • startkde: command not found

© 2022 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright