David

Martin is right. Sorry. He usually is.

A WR lock is a transient lock, it is held only during the time a process is
attempting to write to / restructure a group. For whatever reason, a process
(possibly the previous write) has crashed or the write has entered a loop
(screwed pointers) or hit a semaphore/memory issue when trying to extend.
Whichever, there is a good chance that file is now stuffed. Fortunately
these things are very, very rare. Unfortunately, you've been hit. As for the
cause: often it is something outside of UniVerse, hardware/bus error or some
external process affecting the file.

Since you're unlikely to reproduce the same circumstances, the only real
options are to monitor, watch and check your backups. And hope it doesn't
happen again..

Bad luck.

BTW if it's a small file with a single item, why is it dynamic? That's
pointless overhead.

Brian

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> Norman, David (Health)
> Sent: 27 July 2009 06:18
> To: '[email protected]'
> Subject: [U2] "WR" Group Lock
> 
> In what situations can a WR lock be held on a group and not 
> released ? (UV10.0.16 HP-UX 11i) We've had this situation in 
> one of our test (fortunately) accounts and can't explain it.
> All users got stuck waiting for the group lock to be released 
> - we couldn't even LIST or COUNT the file.
> 
> Active Group Locks:                                    Record 
> Group Group Group
> Device.... Inode....  Netnode Userno  Lmode G-Address.  Locks 
> ...RD ...SH ...EX
> 1073807361     90021        0     31   7 IN          1      5 
>     0     0     0
> 1073807361     10483        0     73  19 IN        800      2 
>     0     0     0
> 1073807361     52985        0     73  24 WR          0      0 
>     0     0     0
> 
> I would also have thought that there would have been a number 
> in the Group EX column.
> We had to log out the user with a kill -9 and unlock their 
> locks as a kill -15 had no effect.
> The file in question is dynamic, with a modulus of 1 and only 
> had 1 record in it (mildly overflowed).
> I have read Martin Phillips' explanation of group locks, and 
> favour his technical suggestion that in this situation "your 
> system is stuffed".
> The notes for the Internals course don't help either.
> 
> Any comments would be appreciated !
> ========================
> David Norman
> Senior Software Engineer - SA Ambulance Service
> 
> ICT Services
> SA Health
> Government of South Australia
> 
> Box 3, GPO
> Adelaide, South Australia 5001
> *+61 8 8274 0384
> * fax +61 8 8271 4844
> * 
> [email protected]<mailto:norman.da...@saambulanc
> e.com.au>
> 
> 
> This e-mail may contain confidential information, which also 
> may be legally privileged. Only the intended recipient(s) may 
> access, use, distribute or copy this e-mail. If this e-mail 
> is received in error, please inform the sender by return 
> e-mail and delete the original. If there are doubts about the 
> validity of this message, please contact the sender by 
> telephone. It is the recipient's responsibility to check the 
> e-mail and any attached files for viruses.
> 
> 
> 
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users
> 

_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to