[lustre-discuss] Upgraded Lustre client now has SElinux failure

Daniel Rodwell daniel.rodwell at anu.edu.au
Tue Aug 4 17:40:00 PDT 2020

Hi Kevin

We've hit the same issue, and reported it up to Whamcloud support. It's being actively worked on.

The public LU and patch is being tracked on LU-13742 (https://jira.whamcloud.com/browse/LU-13742).

Initially we bypassed the issue by setting SELinux to explicitly disabled to get the client mount working on a particular host. The mount fails if SELinux is set to permissive or targeted. This approach may or may not be appropriate for your environment of course :D


Daniel Rodwell
Manager, Data Storage Services
National Computational Infrastructure
The Australian National University
Canberra ACT 2601 Australia

> On 5 Aug 2020, at 4:01 am, Kevin M. Hildebrand <kevin at umd.edu> wrote:
> Hi, I just updated a RedHat machine from RHEL8.1 to RHEL8.2, and Lustre from 2.12.4 to 2.12.5.  I've built the lustre client from source, using Mellanox OFED 5.0-
> After the update, I can no longer mount my Lustre filesystem- I'm getting the following error:
> # mount /lustre
> [ 1482.866631] Lustre: Mounted scratch-client
> [ 1482.882120] SELinux: (dev lustre, type lustre) has no security xattr handler
> [ 1483.048469] Lustre: Unmounted scratch-client
> Has anyone else seen this issue?  
> Thanks,
> Kevin
> --
> Kevin Hildebrand
> University of Maryland
> Division of IT
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20200805/a5ac4abf/attachment.html>

More information about the lustre-discuss mailing list