I'm running quotacheck -avgu on a current machine and it has been 
running for over a day:

  180 v0  I+     0:01.51 quotacheck -avgu 
  181 v0  R+   1380:15.25 quotacheck -avgu 

If I attach to the process I get this :

   181 quotacheck RET   lseek -595088448/0xdc87abc0
   181 quotacheck CALL  lseek(0x5,0,0xdc87abe0,0xffffffff,0)
   181 quotacheck RET   lseek -595088416/0xdc87abe0
   181 quotacheck CALL  lseek(0x5,0,0xdc87ac00,0xffffffff,0)
   181 quotacheck RET   lseek -595088384/0xdc87ac00
   181 quotacheck CALL  lseek(0x5,0,0xdc87ac20,0xffffffff,0)
   181 quotacheck RET   lseek -595088352/0xdc87ac20
   181 quotacheck CALL  lseek(0x5,0,0xdc87ac40,0xffffffff,0)
   181 quotacheck RET   lseek -595088320/0xdc87ac40
   181 quotacheck CALL  lseek(0x5,0,0xdc87ac60,0xffffffff,^C

There is only one disk on the machine that has quotas:

/dev/ccd0d /data ffs rw,userquota 1 4

Which has had its quota file in its root directory modified:
-rw-r-----   1 root  operator  1048576 May 14 16:45 quota.user

Which was shortly after quotacheck was started.

Anyone got an idea on this?

Neil.
--  
Neil J. McRae                                 DNS: Domino Network Services
neil@domino.org         NetBSD/sparc: 100% SpF (Solaris protection Factor)
  Free the daemon in your computer!