Todd and Ted: As a test I decided to copy a 1.9 GB file by drag drop using XP SP2 Explorer to my home volume on athena.mit.edu. The volume is not large enough to hold the file at all.
File h:\ (537235559.1.1) contained in cell athena.mit.edu
Owner jaltman (28180) Group 0
Volume status for vid = 537235559 named user.jaltman
Current disk quota is 1500000
Current blocks used are 1480695
The partition has 97596339 blocks available out of 557143478
Of course, because there is no method by which free AFS partition
and quota space can be reported on a per volume basis, Windows is
given the following info:
2,199,023,254,528 bytes total disk space
1,099,511,627,776 bytes used
1,099,511,626,752 bytes free
50 % in use
This makes the explorer think that there is plenty of room when there
is not. Therefore it proceeds to copy the file. As the space runs
out, fs examine reports:
File h:\ (537235559.1.1) contained in cell athena.mit.edu
Owner jaltman (28180) Group 0
Volume status for vid = 537235559 named user.jaltman
Current disk quota is 1500000
Current blocks used are 1500791
The partition has 97572131 blocks available out of 557143478
Notice that blocks used is greater than the quota. At this point
the AFS file server reports "VOVERQUOTA" which is properly reported
to Windows as "DISK FULL". The "DISK FULL" error is displayed by the
SysInternal's File Monitor. Explorer responds to the "DISK FULL"
error by deleting the partial file and displaying a dialog box with the
title "Error Copying File or Folder" and the error message:
"Cannot copy <filename>: This is not enough free space.
"Delete one or more files to free space, and then try again."
What more do you want Windows to do?
What more do you want OpenAFS to do?
The environment for this test was Windows XP SP2 plus every patch from
Windows Update and OpenAFS 1.4.1 rc4. I only used 1.4.1 RC4 because
that is what was on the machine. The OpenAFS file server is 1.2.11 plus
patches.
If you are running a version of OAFW 1.3.71 or earlier I could
believe you are seeing this problem as in those versions OAFW
returned an Over Quota error to Windows that was not supported by
the CIFS protocol. In 1.3.72 this error was replaced by Disk Full
and the problem was solved.
Once again, I am going to ask, if you have evidence that there is
a problem, please provide evidence.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
