On Thu, Apr 07, 2022 at 12:23:11PM +0200, Sebastien Marie wrote:
On Thu, Apr 07, 2022 at 12:06:45PM +0300, Andrew Krasavin wrote:
On Wed, Apr 06, 2022 at 03:23:55PM +0200, Sebastien Marie wrote:
uvn_io: start: 0xfffffd834f678210, type VREG, use 0, write 0, hold 0, flags
(VBIOONFREELIST)
tag: VT_UFS, ino 19627621, on dev 4, 30 flags 0x100, effnlink 1, nlink 1
mode 0100644, owner 858, group 1000, size 378860088
vn_lock: vnode on freelist: 0xfffffd834f678210, type VREG, use 0, write 0, hold
0, flags (VBIOONFREELIST)
tag: VT_UFS, ino 19627621, on dev 4, 30 flags 0x100, effnlink 1, nlink 1
mode 0100644, owner 858, group 1000, size 378860088
panic: vn_lock: vp on freelist
could you get the filename of the vnode ?
it is located on dev 4,30 (so /dev/sd1o if I didn't mess myself), inode
19627621:
# df | grep /dev/sd1o
/dev/sd1o ... /mount_point_sd1o
# find -x /mount_point_sd1o -inum 19627621 -ls
it is owned by uid 858, which should be (if your user database is consistent
with ports tree) _purritobin user (www/purritobin port).
I will look to do another diff.
Thanks for the testing.
Yes, I'll find out what that file is. Unfortunately, only after I get
home from work.
The user owning uid 858 is the pseudo-user '_qbittorrent' I created.
I originally only wanted to test a new version of
qbittorrent/libtorrent-rasterbar on my laptop before deploying a
similar one on my home server, so the uid was chosen at random
without looking back at uids from the ports tree. This is the wrong
approach, yes.
As for the file whose inode we got thanks to the vprintfs you added,
I can state that it is either a torrent file (*.torrent) or directly
one of the downloaded torrent distribution files (Other files in my
system cannot belong to that user). It is very likely that the file
is part of the torrents for which I ran 'recheck' in order to trigger
the panic. Also, it's likely that the file in the process of which
the panic happens changes/may change every time.
I'll check the full file name and also see if the inode changes with
each new panic. I'll be sure to send the results here.
--
Wbr, Andrew Krasavin
