From: Dave Jones <davej@redhat.com>
Date: Tue, 7 Feb 2006 20:58:48 +0000 (-0800)
Subject: [PATCH] More informative message on umount failure
X-Git-Tag: v2.6.16-rc3~116
X-Git-Url: http://ftp.safe.ca/?a=commitdiff_plain;ds=sidebyside;h=7b4fe29e00a5ab4e778bb24be86d836a25570bc9;p=safe%2Fjmp%2Flinux-2.6

[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>
---

diff --git a/fs/super.c b/fs/super.c
index c177b92..3029421 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -247,8 +247,9 @@ void generic_shutdown_super(struct super_block *sb)
 
 		/* Forget any remaining inodes */
 		if (invalidate_inodes(sb)) {
-			printk("VFS: Busy inodes after unmount. "
-			   "Self-destruct in 5 seconds.  Have a nice day...\n");
+			printk("VFS: Busy inodes after unmount of %s. "
+			   "Self-destruct in 5 seconds.  Have a nice day...\n",
+			   sb->s_id);
 		}
 
 		unlock_kernel();