[OpenAFS] Windows reporting "out of space"
Wed, 13 Jun 2012 15:47:54 -0500
Is the patch rolled into 1.6.1, or does it have to be patched manually?
It's becoming a problem for one of the bigger departments in my company,
so the sooner I can get the upgrade rolled out, the better. Fortunately
we only have six servers.
On 6/13/2012 3:44 PM, Richard Brittain wrote:
> We have finally completed upgrading all our fileservers (all > 2TB
> partitions) to 1.6.1, dafs, with the mentioned patch. This seems to
> mostly solve the 'Out of space' problem, but we can still generate it
> sometimes (Windows 7 only, 1.7.11+ clients). Identifying what
> combination of circumstances actually causes the problem has been like
> nailing jello to a wall. I'll try to submit a bug report with what we
> think is going on.
> All the file servers now return the expected numbers - real or capped
> at 2^31 kB - to 'fs listvol', but sometimes the volume quota and usage
> numbers shown in the Explorer add-on menus are wrong. The numbers
> aren't necessarily wrong when Explorer says 'Out of space' though.
> We've also caused Explorer to abort more than once while investigating
> If I map a network drive rather than navigating the UNC path, explorer
> will write to the location that complains by UNC path.
> The file server upgrade was worth it anyway - 1.6.1 seems to impose a
> lighter load on the server OS, even when hit hard with big volume moves.
> Richard Brittain
> On Mon, 4 Jun 2012, Jeffrey Altman wrote:
>> There is a known bug in the file server that reports negative space
>> for partitions larger than 2TB. A patch has been applied to the
>> and will be included in 1.6.2.
>> commit a64864529d1fca2b5a3f4d21ec598982be335368
>> Jeffrey Altman
>> On Monday, June 04, 2012 2:07:45 PM, Ben Howell wrote:
>>> OpenAFS for Windows 1.7.14, Windows XP and 7, 32- and 64-bit; I don't
>>> have any other versions of the client to test other than the most
>>> recent, but according to some users, this has been ongoing for some
>>> We have one volume on one partition that is 4TB. The approximate space
>>> consumption so far is 1.5TB. If there's any debugging I can do to see
>>> more about what the problem is, please let me know.
>>> - Ben