[CCs added] On Tue, May 12, 2015 at 11:34 AM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: > > Has something changed in FUSE / the kernel in the past few months so > that 'fusermount -u /mp' reports the error: > > fusermount: failed to unmount /mp: Device or resource busy > That's from the umount2() syscall, and most likely not a fuse issue. > and returns a non-zero exit code, but the mountpoint is unmounted > anyway? Is this in 4.1-rc? If so, then the recent fs/namespace.c patches from Eric Biederman would be suspect. Thanks, Miklos > > We have a fusermount wrapper which relies on the fact that fusermount > either succeeds & unmounts; or reports an error & doesn't unmount -- > the wrapper retries in this case. > > Rich. > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
