-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hm. Okay, I can see the real problem lying in the RPCs. Maybe solving this type issue is something to think about for AFS3. We should support 64bit integers. I know it's not common at all to have 20Tb of disk space (or 6.4 for that matter) in a single server, but it will happen. I don't think that requiring anyone in that situation to have 10 /vicep[a-j] is a good solution.
- -Zach Robert Banz wrote: > Datatypes used at various levels within the code, and in the > various volserver-related rpcs... > > You can hack around it (have your fileserver/volserver plateau your > statfs data before using it), but you really don't want to. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGQhK4ZNHVV8XEowIRApy/AKCYxszKhyEp4794UtG5IAQol6qseQCeOhf9 K1lZxNzkSMkBhtqn58mRPIw= =c/uD -----END PGP SIGNATURE----- _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
