lvm2 | Mirror of upstream LVM2 repository

Curently your VG have those gigabytes, check your screens:

In the Armbian community I found a post which answered my question.

Even after installing NFS via apt-get install nfs-kernel-server it only installs the user-space support.

This is the original package info from https://packages.debian.org/sid/nfs-kernel-server:

This package contains the user-space support needed to use the NFS kernel server.

That means what NFS version is supported depends on the kernel on compile time. And even NFSv4 and above is over 10 years only it can be activated/deactivated in the so called kernel config which looks like:

The docs on cppreference say that skip_permission_denied is to "Skip directories that would otherwise result in permission denied errors.". It says nothing about files, only about directories. The option means that in case you cannot read "/proc/sys/xyz" this directory is skipped and no exception is thrown. In your case this is respected and you do not get a filesystem_error exception from recursive_directory_iterator. But that is not related to any file that this iterator returns.

But an exception is thrown in std::filesystem::exists(p) and in std::filesystem::is_directory(p). It is thrown by std::filesystem::status which is internally called by both functions. en.cppreference says that in status "symlinks are followed to their targets". This is not possible for /proc/1/task/1/cwd if you are not root.

ls -alg /proc/1/task/1/cwd shows me a file mode lrwxrwxrwx but a permission denied message.

$ ls -alg /proc/1/task/1/cwd
ls: Lesen der symbolischen Verknüpfung '/proc/1/task/1/cwd' nicht möglich: Keine Berechtigung
lrwxrwxrwx 1 root 0 Mär 11 08:53 /proc/1/task/1/cwd

I believe that the recursive_directory_iterator is only looking at the file mode, but cwd seems to be special and additional access rules apply. So a solution for you could be to catch exceptions thrown by std::filesystem::exists or std::filesystem::is_directory, ignore them and proceed.

Solved the issue. As the boot files were installed in /boot, but the bootloader was installed in /boot/efi, the relative path was the latter rather than the former. Solved it by copying the boot files to a dir inside /boot/efi

You need resize FS. For ext do:

Ok, shortly after posting we figured it out. Seems like a mount point has changed (I expect due to a linux kernel update) and we have not used the nofail option in /etc/fstab as described in the aws knowledge center, this caused the server to hang at boot.

Going forward we will also ensure we use UUID mounting so we are independent on the device naming in /dev/.

What do you mean by storage size? If you mean the amount of storage for Cinder volumes, adjust the CONFIG_CINDER_VOLUMES_SIZE parameter. The documentation isn't clear about it, but I think the number is in Gigabytes. However, this only works if your root filesystem has enough space.

If you mean ephemeral storage, you also need to have a root filesystem that is large enough. I see that your system has three LVM volumes for root, swap and home. My suspicion is that your root volume (named centos-root) is too small. If that is the case, create a Centos installation that does not separate root and home and try again.

Adding additional information to answer the below questions:

The storage size reported in the hypervisor summary refers to the space available in Nova's instances directory, probably under /var/lib/nova (not sure). Which is on your root filesystem.

Packstack uses an LVM volume group as the storage backend for Cinder. The physical volume for that volume group resides on a loop device /dev/loop1, which is a file that resides on the root filesystem. Therefore, Cinder's storage does take up space in your root filesystem. Use the command losetup -a to see that file.

As you just removed the files instead of using apt-get or dpkg to uninstall the package, the package management is not aware of your manual removal, and so apt-get and dpkg still think the newest version is already installed, and so do nothing.

apt-get --reinstall install vagrant

should solve this.