Re: Odd kernel message

["J. Hannken-Illjes" <hannken%mailbox.org@localhost>]

> On 25. Jun 2024, at 19:40, Mike Pumford <mpumford%mudcovered.org.uk@localhost> wrote:
> 
> Never seen this before so I'm not sure what it means:
> 
> [ 18411.785487] vflushbuf: dirty: vnode 0xffffc40eae687040 flags 0x4010<MPSAFE,ONWORKLST>
> [ 18411.785487]         tag VT_UFS(1) type VBLK(3) mount 0xffffc40eacae3000 typedata 0xffffc40eae74bb00
> [ 18411.785487]         usecount 576247 writecount 0 holdcount 11238
> [ 18411.785487]         size 0 writesize 0 numoutput 0
> [ 18411.785487]         data 0xffffc40eae6a5340 lock 0xffffc40eae687200
> [ 18411.785487]         state LOADED key(0xffffc40eacae3000 8) 03 5a 4f 00 00 00 00 00
> [ 18411.785487]         lrulisthd 0xffffffff818bc910
> [ 18411.785487]         tag VT_UFS, ino 5200387, on dev 168, 1 flags 0x0, nlink 1
> [ 18411.785487]         mode 060640, owner 0, group 5, size 0
> 
> Was probably in the middle of a pkgsrc build but not 100% sure of that.

While flushing dirty blocks on a device node new dirty blocks appeared.
In theory this should not happen -- but the vflush will retry anyway.
If you see it one or two times there is no real problem.

--
J. Hannken-Illjes - hannken%mailbox.org@localhost