You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an error using snapper on my home subvolume with some files used by podman and toolbox. There is a character special file in a subfolder of .local/share/containers with the following attributes:
c---------. 1 noeske noeske 0, 0 Feb 15 21:08 fca50e56005e85af082b358efcce51e5ef374a
It seems like snapper is not able to read this file, even with root permissions. I get the following error on trying to get the status of the subvolume:
Therefore, I cannot use snapper status for this subvolume any more. As an interim solution, I created a separate subvolume for .local/share/containers but it would be nice if there is the possibility to handle that otherwise as the folder is now excluded from the backups by snapper.
The trailing dot in c---------. shows that the file has an SELinux security context but no other alternate access method. I assume you should fix that but I am not an expert concerning SELinux so I cannot help here.
Hello,
I have an error using snapper on my home subvolume with some files used by podman and toolbox. There is a character special file in a subfolder of
.local/share/containers
with the following attributes:It seems like snapper is not able to read this file, even with root permissions. I get the following error on trying to get the status of the subvolume:
Therefore, I cannot use
snapper status
for this subvolume any more. As an interim solution, I created a separate subvolume for.local/share/containers
but it would be nice if there is the possibility to handle that otherwise as the folder is now excluded from the backups by snapper.I'm using Fedora Linux 35 with snapper version
If there is any additional information that I can/should provide, I'm happy to provide it.
The text was updated successfully, but these errors were encountered: