Hello. After upgrade to sys-boot/grub-2.00_p5086 I have the following warning(?) messages during grub2-mkconfig invocation: File descriptor 4 (pipe:[1016827]) leaked on vgs invocation. Parent PID 28778: /usr/sbin/grub2-probe File descriptor 5 (pipe:[1016826]) leaked on vgs invocation. Parent PID 28778: /usr/sbin/grub2-probe File descriptor 4 (pipe:[1017877]) leaked on vgs invocation. Parent PID 28787: /usr/sbin/grub2-probe File descriptor 5 (pipe:[1017876]) leaked on vgs invocation. Parent PID 28787: /usr/sbin/grub2-probe File descriptor 4 (pipe:[1017896]) leaked on vgs invocation. Parent PID 28794: /usr/sbin/grub2-probe File descriptor 5 (pipe:[1017895]) leaked on vgs invocation. Parent PID 28794: /usr/sbin/grub2-probe File descriptor 4 (pipe:[1017923]) leaked on vgs invocation. Parent PID 28801: /usr/sbin/grub2-probe File descriptor 5 (pipe:[1017922]) leaked on vgs invocation. Parent PID 28801: /usr/sbin/grub2-probe File descriptor 4 (pipe:[1017338]) leaked on vgs invocation. Parent PID 28808: /usr/sbin/grub2-probe File descriptor 5 (pipe:[1017930]) leaked on vgs invocation. Parent PID 28808: /usr/sbin/grub2-probe Machine boots fine with generated config, but there were no such warnings on grub-2.00-r4. Partition layout: /boot is on RAID 1 via mdadm, / and /var are lvm volumes on top of RAID 5 via mdadm. grub installed via `grub2-install /dev/sd{a,b,c,d}`. Hard drives are GPT formatted. If there is any other needed info I am ready to provide it. Reproducible: Always
Created attachment 355136 [details] emerge --info grub
It seems that sys-fs/lvm2 has a silly "feature" that warns you about "leaked" file descriptors by default. It is easy enough to reproduce: #!/bin/sh exec 3>/dev/null lvs As a workaround, you can set LVM_SUPPRESS_FD_WARNINGS in the environment. The warnings are completely harmless from what I can tell.
Upstream bug in URL.
Thanks for explanation and reporting this upstream.
Do you still see this with grub-2.00_p5107?
(In reply to Mike Gilbert from comment #5) > Do you still see this with grub-2.00_p5107? Just tested it. No such messages are produced anymore. The problem is resolved, thanks.