Re: grub2-mkconfig

Stephen Morris <samorris@xxxxxxxxxxxxxxx> · Mon, 5 Jun 2023 09:22:43 +1000

On 4/6/23 04:33, Patrick Dupre wrote:
  vgs
   VG        #PV #LV #SN Attr   VSize   VFree
   VolSys_1b   1   3   0 wz--n- <40.00g  <4.00g
   VolSys_2    1   3   0 wz--n-  84.50g      0
   VolSys_2b   1   2   0 wz--n- <40.00g <14.00g
# lvs
   LV        VG        Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
   iso-image VolSys_1b -wi-ao----  10.00g
   tmp       VolSys_1b -wi-a-----   1.00g
   usr-src   VolSys_1b -wi-ao----  25.00g
   root      VolSys_2  -wi-a-----  74.53g
   tmp       VolSys_2  -wi-a----- 992.00m
   usr_local VolSys_2  -wi-a-----   9.00g
   tmp       VolSys_2b -wi-a-----   1.00g
   usr-src   VolSys_2b -wi-a-----  25.00g
# pvs
   PV         VG        Fmt  Attr PSize   PFree
   /dev/sda7  VolSys_2  lvm2 a--   84.50g      0
   /dev/sdb5  VolSys_1b lvm2 a--  <40.00g  <4.00g
   /dev/sdb6  VolSys_2b lvm2 a--  <40.00g <14.00g

===========================================================================
  Patrick DUPRÉ                                 | | email: pdupre@xxxxxxx
===========================================================================

Sent: Saturday, June 03, 2023 at 8:11 PM
From: "Roger Heflin" <rogerheflin@xxxxxxxxx>
To: "Community support for Fedora users" <users@xxxxxxxxxxxxxxxxxxxxxxx>
Cc: "stan" <upaitag@xxxxxxxx>
Subject: Re: grub2-mkconfig

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
Hi Patrick, just on this front, I use grub2-mkconfig on my UEFI F38 
system as grubby, which is used by default in Fedora, sometimes does not 
configure grub to load the initramfs at boot time. If your boot system 
is UEFI, then you don't need grub2-install /dev/sda, as that is only 
required for legacy bios boots, but even in the legacy boot mode you can 
still use grub2-mkconfig to build your grub.cfg file.

regards,
Steve

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

_______________________________________________
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

Attachment:
OpenPGP_0x594338B1DE179AB2.asc

Description: OpenPGP public key
Attachment:
OpenPGP_signature

Description: OpenPGP digital signature
_______________________________________________
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