[PATCH] More informative message on umount failure
We had a user trigger this message on a box that had a lot of different mounts, all with different options. It might help narrow down wtf happened if we print out which device failed. Signed-off-by: Dave Jones <davej@redhat.com> Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
parent
1fcbf053e5
commit
7b4fe29e00
|
@ -247,8 +247,9 @@ void generic_shutdown_super(struct super_block *sb)
|
||||||
|
|
||||||
/* Forget any remaining inodes */
|
/* Forget any remaining inodes */
|
||||||
if (invalidate_inodes(sb)) {
|
if (invalidate_inodes(sb)) {
|
||||||
printk("VFS: Busy inodes after unmount. "
|
printk("VFS: Busy inodes after unmount of %s. "
|
||||||
"Self-destruct in 5 seconds. Have a nice day...\n");
|
"Self-destruct in 5 seconds. Have a nice day...\n",
|
||||||
|
sb->s_id);
|
||||||
}
|
}
|
||||||
|
|
||||||
unlock_kernel();
|
unlock_kernel();
|
||||||
|
|
Loading…
Reference in a new issue