This has been discussed on the list before. For 1.6.1, ...
commit a64864529d1fca2b5a3f4d21ec598982be335368
Author: Jeffrey Altman <jalt...@your-file-system.com>
Date: Mon Apr 2 22:35:41 2012 -0400
viced: AFSDisk, AFSFetchVolumeStatus Int31 PartSize
The AFSDisk and AFSFetchVolumeStatus structures use signed
32-bit integers for representation partition size and
available blocks. RoundInt64ToInt31() should be used instead
of RoundInt64ToInt32() when assigning their values.
Change-Id: I3834141fce2d54ce8bdfac3dc566074583bb305e
Reviewed-on: http://gerrit.openafs.org/7022
Reviewed-by: Derrick Brashear <sha...@dementix.org>
Tested-by: Derrick Brashear <sha...@dementix.org>
(cherry picked from commit e8f6dfac59fe042a04a9ac5eb3c37356cb3a22a3)
Reviewed-on: http://gerrit.openafs.org/7023
Reviewed-by: Jeffrey Altman <jalt...@secure-endpoints.com>
Tested-by: Jeffrey Altman <jalt...@secure-endpoints.com>
For 1.4.12, ....
commit 5053d2f4511e180c7c4696fc807b07503b04aa73
Author: Jeffrey Altman <jalt...@your-file-system.com>
Date: Mon Apr 2 22:35:41 2012 -0400
viced: AFSDisk, AFSFetchVolumeStatus Int31 PartSize
The AFSDisk and AFSFetchVolumeStatus structures use signed
32-bit integers for representation partition size and
available blocks. RoundInt64ToInt31() should be used instead
of RoundInt64ToInt32() when assigning their values.
(cherry picked from commit e8f6dfac59fe042a04a9ac5eb3c37356cb3a22a3)
Reviewed-on: http://gerrit.openafs.org/7022
Reviewed-by: Derrick Brashear <sha...@dementix.org>
Tested-by: Derrick Brashear <sha...@dementix.org>
Change-Id: Ieb55d057b09648c88cf1f8596fd934139dde3910
Reviewed-on: http://gerrit.openafs.org/7024
Tested-by: Jeffrey Altman <jalt...@secure-endpoints.com>
Reviewed-by: Jeffrey Altman <jalt...@secure-endpoints.com>
The fix will be included in 1.6.2.
On 12/5/2012 10:14 AM, Frank Burkhardt wrote:
> Hi everybody,
>
> most of our file servers exceed the magical limit of 2TiB per partition.
> When I try to save a file via MS Word 2010 on a volume there, an error
> is shown
>
> "There is not enough disk space. Free enough disk space, and the
> try again."
>
> It seems to be related to the free disk blocks on the partition exceeding
> 2^31 . I'm not quite sure, if my users started using MS Word for files
> on those partitions recently of if the Windows AFS Client's behaviour
> changed during an upgrade. I'm using 1.7.1700 here. Depending on the
> Fileserver's AFS version, doing 'fs exa' on a directory in an affected volume
> shows different kinds of values for the partitions free space:
>
>
> # openafs 1.4.12.1
> $ fs exa my/folder
> [...]
> The partition has 1385923784 blocks available out of -1290650952
> # Wrong: 5.2TiB is available
>
>
> # openafs 1.6.1:
> [...]
> The partition has -1 blocks available out of -1
> # Wrong: 5.4TiB is available
>
>
> Writing those Word files works fine as long as version[fileserver] == 1.4.12
> and (bytesfree[partition] mod 2^42) < 2^41 . Is there a solution to that
> problem?
>
> Best Regards,
>
> Frank Burkhardt
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
signature.asc
Description: OpenPGP digital signature
