FreeBSD 4.x, vinum and vrlock ...

[Marc G. Fournier]

What exactly does this mean?

/proc/43414/status:rsync 43414 42774 23799 14838 5,1 ctty 1107214940,71735 3,779921 33,791868 vrlock 0 0 0,0,0,2,3,4,5,20,31 -
/proc/43479/status:postgres 43479 144 144 144 -1,-1 noflags 1107214989,263828 0,0 1,63591 vrlock 70 70 70,70,70 -
/proc/7/status:bufdaemon 7 0 0 0 -1,-1 noflags 1107140099,155 0,0 61,876619 vrlock 0 0 0,0 -
/proc/9/status:syncer 9 0 0 0 -1,-1 noflags 1107140099,192 0,0 259,373334 vrlock 0 0 0,0 -

I seem to get it a fair amount when I'm starting up a jail, where the 
'umount' in the start scripts just hangs there seemingly indefinitely ...

I'm running 4.10-STABLE #1: Fri Oct 22 15:06:55 ADT 2004 on that machine 
right now, just rebuilt the vinum file system ... doing a search through 
the system source code, the only reference to vrlock is in:

# grep -r vrlock .
./dev/vinum/vinumlock.c:                    tsleep(lock, PRIBIO, "vrlock", 0);

Even after several minutes, that postgres one still has the vrlock:

/proc/43479/status:postgres 43479 144 144 144 -1,-1 noflags 1107214989,263828 0,0 1,665602 vrlock 70 70 70,70,70 -
/proc/44486/status:ctl_cyrusdb 44486 91122 91122 91122 -1,-1 noflags 1107215933,997483 0,44974 0,84574 vrlock 60 60 60,60,60 nsnet.org
/proc/7/status:bufdaemon 7 0 0 0 -1,-1 noflags 1107140099,155 0,0 62,801120 vrlock 0 0 0,0 -
/proc/9/status:syncer 9 0 0 0 -1,-1 noflags 1107140099,192 0,0 259,994279 vrlock 0 0 0,0 -

the funny thing is that if vrlock *is* related to vinum, why is postgres 
in that state, since postgres on this server isn't running on the vinum 
drive ...

---
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664