On Fri, Aug 29, 2014 at 05:47:58PM -0400, Trond Myklebust wrote: > Note that the issue happens with NFSv4 or NFSv4.1 (not NFSv3). That's what I'd been using for testing. > Note that on my system, if I call 'umount' a second time after getting > the 'device is busy' error, then it succeeds. It looks as if the first > call to 'umount /mnt' causes the directory /mnt/export to clear, > causing the second 'umount /mnt' to succeeed (unless I try to access > /mnt/export again): Now, that smells like a different bug - see if commit ab8f2c from -next helps with that one. Anyway, I think I see what's going on; moreover, I have a kinda-sorta solution for the current tree, but it's not something that'll be fun to backport and I'd prefer to look for alternative solutions before going for that one. Hopefully I'll have something postable by tomorrow morning... -- 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
