Hi! I concur with Cliff White. The "lustre_rmmod" returns those sort of errors if there is still a Lustre disk mounted. I have found (with Lustre version 1.6.7.1) that I have to unmount all Lustre disks first (hopefully nicely) and then I can run the lustre_rmmod command typically without errors.
My problems have come from a hung process which cannot be killed accessing a Lustre disk. I have to cycle power to the Lustre client on which the process is hung and the linux shutdown command hangs on trying to remove the Lustre modules. I can't remove the modules while the disk is still mounted (perceived active) and kill -9 PID isn't working. My personal behavior for this is to run the linux shutdown as far it goes (the lustre_rmmod part) and then I physically cycle power on the stuck client box. If there is a better way, I would like to learn it. Cheers! megan _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
