what is vrlock, and why is it causing me problems?

[Dan Nelson]

In the last episode (Feb 01), Marc G. Fournier said:
> 
> /proc/10/status:syncer 10 0 0 0 -1,-1 noflags 1103511247,149 0,0 44097,435728 vrlock 0 0 0,0 -
> /proc/39506/status:postgres 39506 39505 39500 39500 -1,-1 noflags 1106713055,403942 3002,40214 4118,737982 vrlock 1001 1001 1001,1001,1001  maildb.hub.org
> /proc/51927/status:postgres 51927 41068 41068 41068 -1,-1 noflags 1107288042,547570 0,0 1,303423 vrlock 1001 1001 1001,1001,1001  pgsql72.hub.org
> /proc/52582/status:postgres 52582 52581 52579 52579 -1,-1 noflags 1104953811,860872 16534,324197 22783,184956 vrlock 1001 1001 1001,1001,1001  pgsql74.hub.org
> /proc/53309/status:umount 53309 82960 53309 82960 5,2 ctty  1107288298,562659 0,0 0,546634 vrlock 0 0 0,0,0,2,3,4,5,20,31 -
> /proc/54039/status:umount 54039 53941 54039 53941 5,4 ctty  1107288402,928683 0,0 0,526544 vrlock 0 0 0,0,0,2,3,4,5,20,31 -
> /proc/9/status:bufdaemon 9 0 0 0 -1,-1 noflags 1103511247,130 0,0 432,924063 vrlock 0 0 0,0 -

vrlock is an internal vinum lock (see /sys/dev/vinum/vinumlock.c ).

> Load on the server is neglible, so it isn't like I'm dealing with
> 'server lag'
>
> FreeBSD 4.10-STABLE #7: Thu Oct  7 20:17:02 ADT 2004

more like deadlock, I think.  There were two commits in RELENG_4 after
your build time, but it's a performance fix and probably won't affect
your lock problem.

-- 
	Dan Nelson
	dnelson at allantgroup.com