It was exactly what Andrei said it was. Switching from kernel-vanilla to kernel-default resolved the issue. I did a few zypper ref; zypper dup and kernal-vanilla was not offered or get installed. I have no idea how the machine ended up with kernel-vanilla, but the issue of zypper ps showing deleted files in use, even after reboots, is now resolved. Regards, --Moby On 7/22/2022 21:59, Moby wrote:
Thanks Andrei.
You make valid points. In my defense:
1/ This Tumbleweed machine always updates only via zypper ref; zypper dup. I did not ever specify to use a specific kernel.
2/ I had assumed (Wrongly I know now from what you mention) that is was Tumbleweed distro that was switching to a vanilla kernel.
3/ I did not know this was expected behavior. This behavior did indeed start after a few updates ago, the updates again were via zypper ref; zypper dup
4/ Would zypper dup not put me back on openSUSE packages, including the kernel? Doing a zypper ref; zypper dup, I do not see any kernel packages being offered.
I will browse the openSUSE Tumbleweed repo and see what kernel it offers, though now I am a bit concerned as to how this kernel got on the machine to begin with.
Regards,
--Moby
On 7/22/2022 16:06, Andrei Borzenkov wrote:
On 22.07.2022 23:55, Moby wrote:
Thanks Andrei, I guess my eyes are not what they used to be!
On 7/22/2022 15:37, Andrei Borzenkov wrote:
On 22.07.2022 20:54, Moby wrote:
From what I gathered from the link provided by Andrei (https://github.com/lsof-org/lsof/blob/bcc125b7c2a160da019dd8089b999bc6d34866...),
zypper ps may have issues if the device or inode or both of a file do not match. I chased one of the files (/usr/lib64/libaudit.so.1.0.0) and find that the device and inode match between /proc/1270/maps and stat.
No, they do not.
cat /proc/1270/maps ... 7f671edd2000-7f671edd6000 r--p 00000000 00:20>> 39055104 /usr/lib64/libaudit.so.1.0.0 ... stat /usr/lib64/libaudit.so.1.0.0 File: /usr/lib64/libaudit.so.1.0.0 Size: 116800 Blocks: 232 IO Block: 4096 regular file Device: 0,35 Inode: 39055104 Links: 1 So this is device 0,32 in /proc/.../maps and device 0,35 in stat. Yes, you are correct, /proc/1270/maps shows the file as 0,32 while stat shows 0,35
Which kernel and root filesystem are you using (more precisely - what filesystem where /usr/lib64 is located)? It is a vanilla kernel:
uname -a Linux esilinux2.ad.techspace.cc 5.18.11-1-vanilla #1 SMP PREEMPT_DYNAMIC Fri Jul 15 05:36:11 UTC 2022 (4fcb983) x86_64 x86_64 x86_64 GNU/Linux
And the reason you never mentioned it in the first place is ... ? When you post to openSUSE list everyone expects that you are using openSUSE packages. If you are using unmodified upstream version you either tell it or ask upstream.
This is expected behavior and there is no way it could "have started a couple of weeks ago" unless you have been using openSUSE kernel before.