[lustre-discuss] segfault with 2.15.8 client on AlmaLinux 9.7

Andreas Dilger adilger at thelustrecollective.com
Mon Jun 8 18:38:50 UTC 2026


Hi Steve,
I haven't seen this issue before.  Some things to test out:
- does it work if you run the latest lfs/liblustreapi from master?  It may be fixed already.
- does it work if you run non-interactively, like "lfs setstripe -c 2 ."?
- does it work if you run from the parent dir, like "lfs setstripe -c 2 DIR"?
- what does "strace lfs setstripe -c 2 ." show?
- if you run under GDB, can you report the exact spot where it is crashing?

If it can be reproduced with master lfs/liblustreapi please file a Jira ticket with details.

Cheers, Andreas

> On May 29, 2026, at 10:22, Steve Kirk via lustre-discuss <lustre-discuss at lists.lustre.org> wrote:
> 
> Hi,
> 
> I've noticed I get a segfault if I do the following:
> 
> lfs > setstripe -c 2 .
> lfs: unable to open '/lib64/libgcc_s.so.1': Permission denied (13)
> lfs: Segmentation fault (core dumped)
> 
> I'm left with a zero-size file in the directory called:
> 'f.'$'\017\037\204'
> 
> libgcc_s.so.1 is a symlink; the files are readable by my user account:
> lrwxrwxrwx 1 root root 25 Apr  4 23:17 /lib64/libgcc_s.so.1 -> libgcc_s-11-20240719.so.1
> 
> If I specify the name of a directory, everything works as expected. I have the following RPMs installed, synced from the whamcloud repo:
> kmod-lustre-client-2.15.8-1.el9.x86_64
> lustre-client-2.15.8-1.el9.x86_64
> 
> Is this a known issue?
> 
> Regards,
> Steve
> 
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

---
Andreas Dilger
Principal Lustre Architect
adilger at thelustrecollective.com





More information about the lustre-discuss mailing list