FB <[EMAIL PROTECTED]> writes:
> Unfortunately, The statfs()-problem remains - AFS still shows zero
> remaining blocks which confuses some "clever" programs.
At least in my case, the problem is the reported block *size*, which
comes back as 2^64 - 1 -- so while I also get absurd numbers, they're
at least absurdly high rather than absurdly low:
$ df -BE /afs
Filesystem 1E-blocks Used Available Use% Mounted on
AFS 144000000E 0E 144000000E 0% /afs
$ stat -f /afs
File: "/afs"
ID: 6300001234 Namelen: 256 Type: UNKNOWN (0x0)
Block size: 18446744073709551615 Fundamental block size: 18446744073709551615
Blocks: Total: 9000000 Free: 9000000 Available: 9000000
Inodes: Total: 9000000 Free: 9000000
afs_statfs appears to be getting the block size from sbp; being too
lazy to instrument the code, I'm not sure which structure's getting
corrupted.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
