4.1.3 and above, for sure, return a warning that you have gone over your soft quota, and the write succeeds. Solaris 2.x also works as expected.
I.e., you don't expect Solaris 2.x to print a warning?
diddy$ uname -sr SunOS 5.6 diddy$ df . Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s1 245911 4634 241032 2% /var diddy$ mount | egrep /var /var on /dev/dsk/c0t0d0s1 read/write/setuid/quota/largefiles on Wed Nov 12 15:55:16 1997 diddy$ quota -v | head -3 Disk quotas for guy (uid 75): Filesystem usage quota limit timeleft files quota limit timeleft /var 0 16 32 0 4 8
diddy$ dd if=/dev/zero of=file1 bs=1024 count=16 16+0 records in 16+0 records out diddy$ quota -v | head -3 Disk quotas for guy (uid 75): Filesystem usage quota limit timeleft files quota limit timeleft /var 16 16 32 7.0 days 1 4 8
No warning message printed when I went over the soft quota - even on a *local* file system.
I know 4.x prints one for local file systems - it got that from BSD. However, 4.1.4 doesn't print one for NFS-mounted file systems:
nova% uname -sr SunOS 4.1.3 nova% df . Filesystem kbytes used avail capacity Mounted on diddy:/var/tmp 245911 4635 241031 2% /mnt nova% dd if=/dev/zero of=file1 bs=1024 count=16
and "quota -v" on "diddy" reports:
diddy$ quota -v Disk quotas for guy (uid 75): Filesystem usage quota limit timeleft files quota limit timeleft /var 16 16 32 7.0 days 1 4 8
so I *did* go over the soft quota - I just didn't get told about it until I ran "quota" on "diddy".
Yes, we can do soft quotas.
We can't, however, do them the way they work on a *locally-mounted file system* - just as is the case with other NFS servers, the only indication you will get when you go over a soft quota is the indication you get when you run "quota".
If that's acceptable to everyone, we can put that on the schedule; there's no technical problem with providing soft quotas compatible with those you get from a SunOS 4.x or 5.x *NFS server* when a *client* goes over the soft quota.
If it's *not* acceptable, we can see what kind of notification we can provide. As per the above, we can't provide the same kind of notification you get on locally-mounted file systems, because the SunOS 4.x and 5.x kernels don't provide that (heck, the 5.6 kernel, at least, doesn't even provide it for *local* file systems); however, we could have it send mail, or something such as that.