Messages in this thread | | | Date | Wed, 19 Dec 2001 23:15:37 +0100 | From | Alex Riesen <> | Subject | 2.4.17-rc2: VFS: Busy inodes after unmount. Self-destruct... |
| |
Dec 19 23:01:24 steel automount[3628]: mount(nfs): mounted dale.home:/ on /net/dale Dec 19 23:05:38 steel automount[3624]: shutting down, path = /net Dec 19 23:05:38 steel automount[3624]: >> umount: /net/dale: device is busy Dec 19 23:05:38 steel automount[3624]: could not unmount /net/dale Dec 19 23:05:38 steel automount[3624]: >> umount: /net: device is busy Dec 19 23:06:51 steel kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
no self-destruct, of course, but the first 5 seconds wasn't so wonderful :) I had the automount 3.1.7 running. Auto-mounted a nfs node, got in, tried unmount, got 'busy', went out of the mounted directory, tried to unmount master directory (and failed), unmounted the nfs-mounted directory, unmounted the automount master directory.
The question is just: is that bad?
-alex
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |