try typing vgs/lvs/pvs and see if that also gets the warning. Some prior centos version did also have this error for a while, I never noticed any real issue with the programs reporting this. For the most part this is just some attempt at reporting a "leaked" file descriptor. I am not sure how one leaks a file descriptor as all file descriptors owned by a process disappear when the process goes away. They may simply be reporting file descriptors that are still "open" when the program exits (not properly closed), which so long as it is not a file you are writing to(and have an unsynced buffer in program ram still), then it is not an actual problem (it is likely somewhat poor coding practices). It likely means someone forgot to turn off some debugging options and also forgot to close some file that not closing it has no real impact on the program function. On Sat, Jun 3, 2023 at 9:09 AM stan via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, 2 Jun 2023 13:18:47 +0200 > Patrick Dupre <pdupre@xxxxxxx> wrote: > > > Hello, > > > > On a machine with a triple boot (an 3 HD, all fedora), I get a > > bunches of > > > > File descriptor 3 (pipe:[240388]) leaked on vgs invocation. Parent > > PID 75317: grub2-probe > > > > when I run grub2-mkconfig > > I have /boot/efi (UEFI) on /dev/sda3 (in fat16) > > and > > grub2 core.img on /dev/sda1 > > > > Can I fix this? > > > > In addition, > > What are your recommendations for running (which systems) > > grub2-mkconfig > > and > > grub2-install /dev/sda > > I never see that error when I run grub2-mkconfig, in both uefi and > legacy. So, I suspect there is something about the way your system is > set up causing the issue. > > A search turned up this link that describes the cause and a workaround. > https://superuser.com/questions/1437911/file-descriptor-3-leaked-on-vgcfgbackup-invocation-parent-pid-bash > Other links explained that this is happening in the lvm utilities, and > is harmless, basically a warning. You must have lvm enabled, and the > grub2-mkconfig is probing them, and triggering lvm to issue this error. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
