Hi list,
I'm seeing an occasional issue where an SELinux file context is
applied on a cluster node to a file on a GFS1 filesystem, but the old
context remains on one (or more) other nodes.
A simple 'restorecon /path/to/file' fixes the context on the "broken"
node.
We're running CentOS 5.2 x86_64 with all the latest stable cluster and
GFS versions.
Any ideas why this could be happening and/or how to debug it?
Thanks,
Tom
--
Tom Lanyon
Systems Administrator
NetSpot Pty Ltd
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster