Describe the bug
In https://discussion.fedoraproject.org/t/kernel-fails-to-update-automatically-to-7-0-x-due-to-dracut-error/191371 we got a report from a Fedora user that dracut failed with errors like dracut-install: ERROR: cannot mmap '/var/tmp/dracut.dOlGFcB/initramfs/usr/lib64/libnss_myhostname.so.2;69c039c9': Invalid argument.
Distribution used
Fedora 44
Dracut version
Likely 108
Init system
systemd
To Reproduce
It looks like - create a file with a name like /usr/lib64/libnss_myhostname.so.2;69c039c9 and run dracut. Not sure if it has to be a 'real' library file
Expected behavior
Dracut should work, probably by ignoring the file
Additional context
We don't know what caused these files to exist, but it does seem like dracut should not be tripped up by the existence of this kind of orphaned temporary file or whatever it turns out to have been.
Describe the bug
In https://discussion.fedoraproject.org/t/kernel-fails-to-update-automatically-to-7-0-x-due-to-dracut-error/191371 we got a report from a Fedora user that dracut failed with errors like
dracut-install: ERROR: cannot mmap '/var/tmp/dracut.dOlGFcB/initramfs/usr/lib64/libnss_myhostname.so.2;69c039c9': Invalid argument.Distribution used
Fedora 44
Dracut version
Likely 108
Init system
systemd
To Reproduce
It looks like - create a file with a name like
/usr/lib64/libnss_myhostname.so.2;69c039c9and run dracut. Not sure if it has to be a 'real' library fileExpected behavior
Dracut should work, probably by ignoring the file
Additional context
We don't know what caused these files to exist, but it does seem like dracut should not be tripped up by the existence of this kind of orphaned temporary file or whatever it turns out to have been.