It's not tragic by any means, but it's a slight annoyance that would be nice to correct. I've heard some mention that it is a kernel bug unrelated to afs, does anyone have any more details on this? Is it possible that afsd/libafs module is not properly closing the cache inodes that it opened? They are not opened in user space, that's clear, but the kernel still thinks the filesystem is in use, so there must be something opened. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
