In message <[EMAIL PROTECTED]>,Derr ick J Brashear writes: >That's not really a fix, it's a workaround.
i did say quick fix. >> in the long term the linux afs client could be made to just keep growing >> the number of afs inodes as necessary. for 2.6 these inodes come from >> a dynamic pool. this might slow down some afs operations though since > >We should probably actually look at doing it this way. i dont think afs_vcount/afs_maxvcount can be eliminated entirely for linux. you still need to shake the dcache tree periodically. perhaps afs_maxvcount should be doubled when it gets exceeded (with an optional warning). _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
