Tobias, File a bug report against the application that is querying volume information for the root directory of a drive mapping instead of for the path that the application is actually interested in. The AFS redirector reports each volume change in the path as a reparse point. It is up to the application to query for free space in the correct volume. A readonly volume by definition has zero bytes free.
As a work around for applications that cannot be fixed, use a drive letter mapping to the root of the volume you wish the application to access. Jeffrey Altman On 1/23/2013 3:42 AM, Tobias Doerffel wrote: > Hi, > > I'm having the problem that AFSRDRFsd doesn't report the correct quota > state/free space when mounting an AFS path with a readonly volume in > the root directory. Instead of the real free space it always reports 0 > bytes for the drive which is wrong. This leads to problems when > copying files to a RW-submount in that drive which definitely has > sufficient free space while e.g. the Windows explorer only evaluates > the free space of the drive. I tried setting a big quota value for the > root volume but this doesn't help. Free space remains at 0 bytes. This > happens with the 1.7.x series on Win32. Is this behaviour intended and > if so, is there any workaround for the file copy issue? > > Thank you very much in advance! > > Best regards > > Tobias > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
smime.p7s
Description: S/MIME Cryptographic Signature
