Il giorno Ven 28 Mag 2010 12:29:24 CET, Dejan Muhamedagic ha scritto: > Hi,
Hi Dejan, thanks for your answer. [...] >> the only way to make things work again is to cleanup the nfs_clone >> resource (or restart the nfs-kernel-server daemon) and then cleanup the >> store group. It seems that the filesystem is keep opened by the nfs daemon. > Which it shouldn't. The lsb:nfs-kernel-server should've exited > only once the server was really stopped. Note that the nfs-kernel-server isn't connected to the exportfs, but is only a cloned resource, so it isn't touched by the migration process. >> So, what's the difference between a simple copy and a rsync? Why with >> rsync the fs resource isn't able to unmount the filesystem? > Did you try strace with rsync to see what is different? I made some other tests and the problem appear also with cp, so it is not an rsync-related issue. >> There is >> something I am missing or this should be an fs resource agent bug? > Not strictly a Filesystem RA bug, though it could behave better. > Currently, the stop operation fails quickly (in six seconds) in > case there's something using the filesystem, which won't go away. > As is the case with kernel threads. You can try the attached > patch with which the Filesystem RA is going to wait until the > defined stop timeout for the filesystem to be unmounted. Short > instructions: set the fast_stop parameter to "no" and set the > timeout for the stop operation of the filesystem to however long > the nfsd takes to exit. > Thanks, > Dejan I will give the patch an immediate try and let you know. Thanks again! -- RaSca Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene! [email protected] http://www.miamammausalinux.org _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
