I have container using a root disk in a thin lvm. At some point today, I got input/output error from docker running in that container. The root disk itself has enough free space, but the thin lvm for that root disk says 100% allocation. Could this be the reason for the I/O errors?
So I tried cloning the container to another storage with enough free space. Unfortunately, the clone fails with a couple of messages like these:
Running fsck /dev/pve/vm-100-disk-0 in the proxmox shell reports the same problems but fails to repair anything with this message;
Is this because pve-vm--100--disk--0 is still mounted and/or what can do I need to do to fix that fs problem? (the container is stopped obviously)
Any help is appreciated!
So I tried cloning the container to another storage with enough free space. Unfortunately, the clone fails with a couple of messages like these:
Code:
rsync: [sender] readlink_stat("/var/lib/lxc/104/.copy-volume-2/usr/share/doc/tar/NEWS.gz") failed: Structure needs cleaning (117)
...
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1330) [sender=3.2.3]
Logical volume "vm-104-disk-0" successfully removed
TASK ERROR: clone failed: command 'rsync --stats -X -A --numeric-ids -aH --whole-file --sparse --one-file-system '--bwlimit=0' /var/lib/lxc/104/.copy-volume-2/ /var/lib/lxc/104/.copy-volume-1' failed: exit code 23Running fsck /dev/pve/vm-100-disk-0 in the proxmox shell reports the same problems but fails to repair anything with this message;
Code:
Error writing file system info: Input/output error
/dev/mapper/pve-vm--100--disk--0: ***** FILE SYSTEM WAS MODIFIED *****Is this because pve-vm--100--disk--0 is still mounted and/or what can do I need to do to fix that fs problem? (the container is stopped obviously)
Any help is appreciated!