vjbod is the virtual jbod provided by QNAP.
It’s QNAP’s additions to libc. It really should not have been placed there. It should have been placed differently in the filesystem layer. I suspect it’s part of their Q-Tier system (which I do not use)
It looks like Plex because PMS calls into libc() to do I/O.
In QNAP’s libc(), it routes through and into their vjbod handler to deal with your configuration, which is where it faults.
I did have the vjbod installed, but have removed it. Errors still show it though. Planning a reboot later tonight.
So you think I should send these logs to qnap?
Yes please do send them to QNAP.
Report it as a VJBOD bug causing segfaults in user-space programs.
You can even reference Plex (I chat with them frequently)
Go ahead and reboot it to remove vbjod from memory
will do, and let you know what qnap says.
Im currently disabling the SSD cache at present, so itll take a few hours to flush the cache out being 2.7TB, once done ill reboot and check that diag log again.
not sure if it would be relevant to this or not, but wondering if this could be the cause of a kworker process always using about 10 to 15% cpu time. Ive had this issue for many months though. On a reboot it, its normal, then about an hour later, it starts and never settles untill a reboot, then the cycle starts over again.
so im just thinking if theres something matching up here somewhere, considering the kworker is a kernel process
anyway to PM you ChuckPA
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
