LVM2 installation error report

For Developers
1

Hello,

Was installing LVM2 on my "wd mybook single"

During installation of LVM2 the following errors showed up.

LVM2 appears to have installed correctly and I don't know the significance (if any) of these errors.

So, just posting this to report.

root@backup:~# opkg install lvm2
Installing lvm2 (2.03.22-1) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0/packages/powerpc_464fp/packages/lvm2_2.03.22-1_powerpc_464fp.ipk
Installing libreadline8 (8.2-1) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0/packages/powerpc_464fp/base/libreadline8_8.2-1_powerpc_464fp.ipk
Installing libaio (0.3.113-2) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0/packages/powerpc_464fp/packages/libaio_0.3.113-2_powerpc_464fp.ipk
Installing libdevmapper (1.02.196) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0/packages/powerpc_464fp/packages/libdevmapper_1.02.196_powerpc_464fp.ipk
Configuring libreadline8.
Configuring libaio.
Configuring libdevmapper.
Configuring lvm2.
File descriptor 3 (/tmp/lock/opkg.lock) leaked on lvm invocation. Parent PID 228                                                                                                                                                                                5: /bin/sh
File descriptor 3 (/tmp/lock/opkg.lock) leaked on lvm invocation. Parent PID 228                                                                                                                                                                                5: /bin/sh
root@backup:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root               102.3M     33.0M     67.3M  33% /
tmpfs                   122.2M    932.0K    121.3M   1% /tmp
/dev/sda1                 8.0M      4.0M      3.6M  52% /boot
tmpfs                   512.0K         0    512.0K   0% /dev
root@backup:~# opkg install lvm2
Package lvm2 (2.03.22-1) installed in root is up to date.
root@backup:~# lvc
lvchange   lvconvert  lvcreate

I will post back here if there are further LVM2 related issues.

2

Leaked file discriptor is basically a 'security' warning from the lvm tool - notifies a user that application that has forked the lvm 'leaded' descriptor fd==3 (pointing to .lock file)

So 'opkg' application should be actually fixed and likely open the lock file with O_CLOEXEC or eventually close the descriptor before forking another app - as there is no reason to let forked application to manipulate with its files.

Also the warning itself can be disabled with: export LVM_SUPPRESS_FD_WARNINGS=1