Bug #349
closed
conflict with vnode
0%
Description
I am getting a number of these warnings during heavy disk I/O (such as
extracting a large tar, or even compiling from pkgsrc)
Oct 13 16:54:40 dfly kernel: conflict with vnode 0xd34cd600
Oct 13 16:54:40 dfly kernel: Warning: inode free race avoided 1 times
Oct 13 16:58:09 dfly kernel: conflict with vnode 0xd34d2800
Oct 13 16:58:09 dfly kernel: Warning: inode free race avoided 1 times
DragonFly dfly.home.local 1.6.1-RELEASE DragonFly 1.6.1-RELEASE #0: Sat Oct 7
12:27:33 CEST 2006 root@chlamydia.fs.ei.tum.de:/usr/obj/usr/src/sys/GENERIC
i386
Oct 13 12:28:33 dfly kernel: aac0: <Dell PERC 2/Si> mem 0xf4000000-0xf7ffffff
irq 14 at device 2.1 on pci0
Oct 13 12:28:33 dfly kernel: aac0: i960RX 100MHz, 54MB cache memory, no battery
support
Oct 13 12:28:33 dfly kernel: aac0: Kernel 2.8-0, Build 6089, S/N 3801d0
Oct 13 12:28:33 dfly kernel: aac0: Supported
Options=2558<DATA64,HOSTTIME,WINDOW4GB,SOFTERR,SGMAP64>
The system continues to function properly as far as i can tell.
Updated by dillon about 18 years ago
:I am getting a number of these warnings during heavy disk I/O (such as
:extracting a large tar, or even compiling from pkgsrc)
:
:Oct 13 16:54:40 dfly kernel: conflict with vnode 0xd34cd600
:Oct 13 16:54:40 dfly kernel: Warning: inode free race avoided 1 times
:Oct 13 16:58:09 dfly kernel: conflict with vnode 0xd34d2800
:Oct 13 16:58:09 dfly kernel: Warning: inode free race avoided 1 times
These can be ignored. In fact, I will take out the warning now.There was an inode-reuse race that was fixed a long time ago. I added
the printf's to print out when the race would have occured if not for
the fix. This is the comment in the code:/*
* Check to see if an inode is in the hash table. This is used to interlock
* file free operations to ensure that the vnode is not reused due to a
* reallocate of its inode number before we have had a chance to recycle it.
*/
In anycase, just ignore it.-Matt