On 3/13/2013 3:50 PM, Andy Malato wrote: > ! There is no such specific limitation. There are some bugs in 1.4 for > ! "large" volumes in general, but not around the 2TB mark specifically. > ! And there is a problem with space reporting for volumes and partitions > ! larger than 2TB, but they still work (except when you try to write to > ! them via a modern Windows client). > > Can you elaborate on the issue you mention about writing to large > volumes with a modern Windows client ? Can you define "modern Windows > Client?" Does this include the latest 1.7.x release of the Windows > client ? From what you say it sounds like these write issues are client > related and not tied to the server version or is that not the case ? > Perhaps these issues are fixed in the 1.6.x server version ? > > This is of a concern to us as we have a large number of Windows OpenAFS > clients deployed at our site.
The issue is that the RPC used to report partition size, volume quota, and free space cannot represent more than 2^31 1K blocks. The 1.4.x file servers attempt to cap the reported sizes but got it wrong. They cap the reported values at 2^32 1K blocks and if you partition size or free space is larger than 2^31 1K blocks, the reported value will appear to the client as a negative number. The 1.7.x Windows clients perform free space checks as part of processing an extending write. This is to ensure that applications do not write data to the page cache that cannot later be flushed to the file server. 1.6.2 properly caps the reported values to 2^31 1K blocks.
smime.p7s
Description: S/MIME Cryptographic Signature
