The user/group used can be out of date by a few seconds, same as the "used"
and "referenced" properties. You can run sync(1M) to wait for these values
to be updated. However, that doesn't seem to be the problem you are
encountering here.
Can you send me the output of:
zfs list zpool1/sd01_mail
zfs get all zpool1/sd01_mail
zfs userspace -t all zpool1/sd01_mail
ls -ls /export/sd01/mail
zdb -vvv zpool1/sd01_mail
--matt
Jorgen Lundman wrote:
Are there way to force ZFS to update, or refresh it in some way when the
user quota/used value is not true to what is the case? Are there known
way to make it out of sync that we should avoid?
SunOS x4500-11.unix 5.10 Generic_141445-09 i86pc i386 i86pc
(Solaris 10 10/09 u8)
zpool1/sd01_mail 223M 15.6T 222M /export/sd01/mail
# zfs userspace zpool1/sd01_mail
TYPE NAME USED QUOTA
POSIX User 1029 54.0M 100M
# df -h .
Filesystem size used avail capacity Mounted on
zpool1/sd01_mail 16T 222M 16T 1% /export/sd01/mail
# ls -lhn
total 19600
-rw------- 1 1029 2100 1.7K Oct 20 12:03
1256007793.V4700025I1770M252506.vmx06.unix:2,S
-rw------- 1 1029 2100 1.7K Oct 20 12:04
1256007873.V4700025I1772M63715.vmx06.unix:2,S
-rw------- 1 1029 2100 1.6K Oct 20 12:05
1256007926.V4700025I1773M949133.vmx06.unix:2,S
-rw------- 1 1029 2100 76M Oct 20 12:23
1256009005.V4700025I1791M762643.vmx06.unix:2,S
-rw------- 1 1029 2100 54M Oct 20 12:36
1256009769.V4700034I179eM739748.vmx05.unix:2,S
-rw------T 1 1029 2100 2.0M Oct 20 14:39 file
The 54M file appears to to accounted for, but the 76M is not. I recently
added a 2M by chown to see if it was a local-disk, vs NFS problem. The
previous had not updated for 2 hours.
# zfs get useru...@1029 zpool1/sd01_mail
NAME PROPERTY VALUE SOURCE
zpool1/sd01_mail useru...@1029 54.0M local
Any suggestions would be most welcome,
Lund
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
