On Wed, 2010-06-23 at 15:17 -0400, Chuck Lever wrote: > On 06/23/10 02:06 PM, Staubach_Peter@xxxxxxx wrote: > > Perhaps the oprofile support is retaining an additional reference to the in-core > > inode which is causing the .nfsXXXX files to get created and is also delaying their > > removal? > > The files do not appear in oprofiled's fd list (in /proc). Killing the > oprofiled process after the test finishes does make those files go away. > Just shutting down the profiler leaves oprofiled, so additionally > killing the daemon appears to be necessary to finish the silly removal > process. > > These files are all executables (part of the connectathon suite), but I > don't have the "profile user space binaries" checkbox selected. OK. That makes more sense... Do these files perhaps appear in the /proc/<pid>/maps and/or /proc/<pid>/smaps pseudofile for oprofiled? Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
