Followup:
The startup problem has been fixed by removing /var/cache/openafs/* and making the cache smaller. Now 5GB. * is there a max size of the cache? * is there some check for that max size (to prevent unsupported or unreasonable big values in cacheinfo)? Looks to me that openafs tries to create a 5TB on a 1TB HD if asked to do so. But I have a new problem: Old AFS client: $ ls /afs/stacken.kth.se/home | wc -l 739 New AFS client: $ ls /afs/stacken.kth.se/home | wc -l 775 Of course my home (haba) is one of the missing ones. But even if I see the mount point with ls, it may not exists anyway: $ ls /afs/stacken.kth.se/home | head -1 aalen $ fs lsm /afs/stacken.kth.se/home/aalen fs: File '/afs/stacken.kth.se/home/aalen' doesn't exist So what is going on? I can access $ ls /afs/grand.central.org/software/openafs/|wc -l 245 $ fs checks All servers are running. $ fs getcac AFS using 1924 of the cache's available 5000000 1K byte blocks. Regards, Harald. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
