On Thu, Jan 29, 2015 at 4:55 PM, Cyril Hrubis <chru...@suse.cz> wrote: > Hi! >> >> Yupp, that popped up. >> >> How can I disable that gvfsd (here: Ubuntu/precise? >> > >> > Just kill the process, or run the testcases via ssh session. >> > >> >> And can this issue be documented? >> > >> > Hmm, maybe we can change the test cases to complain loudly if the >> > process is found running. >> > >> >> Good idea. > > And should be fixed in latest git. Now the testcases complain about the > failure, give a hint what may be causing it, and if the umount() is not > the the syscall under test, it's retried a few times with short usleep > between. >
Thanks for fixing this! For followers, here the fix [1]... commit 10b61174ce0019833cc4c2e95ddbeec723131920 "syscalls: umount01: Give a hint on failure with EBUSY" For the sake of completeness (here: Ubuntu/precise)... # ps axu | grep v[f]s wearefam 2006 0.0 0.1 54068 5044 ? S 08:55 0:00 /usr/lib/gvfs/gvfsd wearefam 2008 0.0 0.1 207920 5656 ? Sl 08:55 0:00 /usr/lib/gvfs//gvfs-fuse-daemon -f /home/wearefam/.gvfs wearefam 2056 0.0 0.1 72228 7224 ? S 08:56 0:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor wearefam 2070 0.0 0.0 143600 3788 ? Sl 08:56 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor wearefam 2075 0.0 0.1 61852 5440 ? S 08:56 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor wearefam 2087 0.0 0.1 58684 6372 ? S 08:56 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/0 wearefam 2089 0.0 0.1 54068 5472 ? S 08:56 0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.6 /org/gtk/gvfs/exec_spaw/1 ( Indeed it's a "gvfsd-trash" instance running :-). ) - Sedat - [1] https://github.com/linux-test-project/ltp/commit/10b61174ce0019833cc4c2e95ddbeec723131920 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
