Actually, I think it's the USB backup that I have mounted:
[root@fedora ~]# df -h /backup
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/external_backup 2.3T 691G 1.5T 32% /backup
It may also have been trying to work on the FUSE mounted directories, I'm not sure. In any case, this is a very unwelcome surprise for anyone with a large filesystem.
This update can be pushed to stable now if the maintainer wishes
For some reason the selinux-policy/container-selinux update is triggering a restorecon relabel on the specified directories.
This involves walking every file on the contents of directories and changing the labels on files.
This update has been submitted for testing by lsm5.
This update's test gating status has been changed to 'ignored'.
lsm5 edited this update.
This update has been pushed to testing.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Works great! LGTM! =)
Is the update supposed to take 5 minutes of full CPU utilization? It was really long.
restorecon
has been running for over an hour with this update (perhaps because I had some large filesystems mounted via sshfs?)Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Actually, I think it's the USB backup that I have mounted:
It may also have been trying to work on the FUSE mounted directories, I'm not sure. In any case, this is a very unwelcome surprise for anyone with a large filesystem.
This update can be pushed to stable now if the maintainer wishes
For some reason the selinux-policy/container-selinux update is triggering a restorecon relabel on the specified directories. This involves walking every file on the contents of directories and changing the labels on files.
Working fine
This update has been obsoleted by container-selinux-2.211.1-1.fc38.