On Tue, Jun 28, 2011 at 05:14, Konstantin Khlebnikov wrote: > Petr Uzel wrote: >> On Tue, Jun 28, 2011 at 12:18:03PM +0400, Konstantin Khlebnikov wrote: >>> commit 33cee6675edecbd27c0628f8b7c74c7d88fc02b2 >>> >>> http://git.kernel.org/?p=utils/util-linux/util-linux-ng.git;a=commitdiff;h=33cee6675edecbd27c0628f8b7c74c7d88fc02b2;hp=fde25e6be6e00a0998eb58b4b9d0d0b9ad65dbfd >>> "umount: allow unmounting loopdev specified by associated file" >>> broke umounting (by mountpoint) for broken nfs mounts, >>> because now umount always call stat() for target argument and umount hang >>> inside nfs-rpc: >> >> Shouldn't this be handled in the kernel? Or is stat() really >> supposed to fail in such way with broken nfs? > > It depends on used mount options, IIRR in "soft" mode it by default fail > with EIO after 3-6 minutes timeout, > in "hard" mode syscalls never returns EIO. i noticed this recently. one of the reasons i love `umount -lf` with broken nfs mounts is that it works immediately. any attempt to access said broken mount in this situation is wrong as it inherently implies it has to wait for a timeout (if one ever comes as Konstantin noted). other than my personal usage on the command line, it makes shutdown scripts obnoxiously slow to the point of being useless. -mike -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
