FreeBSD 4.x, vinum and vrlock ...

Marc G. Fournier scrappy at hub.org
Tue Feb 1 20:02:55 PST 2005


On Wed, 2 Feb 2005, Greg 'groggy' Lehey wrote:

> On Monday, 31 January 2005 at 20:02:50 -0400, Marc G. Fournier wrote:
>>
>> 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 -
>
> It looks like breakage from your MUA.   I've deleted the rest; it's
> too painful.
>
>> 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 ...
>
> If you're talking about the vrlock state, it's used for locking bands
> when updating striped plexes.  If it hangs around for any length of
> time, it'll be a deadlock.  Have you been killing processes?  Has
> anybody else seen this?

I have not been killing processes ... seems to happen more often when I'm 
using rsync to copy a directory hierarchy from one server to the other 
though ...

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


More information about the freebsd-questions mailing list