* [2.6 patch] More informative message on umount failure.
@ 2006-02-07 14:24 Adrian Bunk
0 siblings, 0 replies; only message in thread
From: Adrian Bunk @ 2006-02-07 14:24 UTC (permalink / raw)
To: Andrew Morton; +Cc: Dave Jones, Linux Kernel
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>
---
This patch was sent by Dave Jones on:
- 2 Feb 2006
--- linux-2.6.15.noarch/fs/super.c~ 2006-02-02 20:19:20.000000000 -0500
+++ linux-2.6.15.noarch/fs/super.c 2006-02-02 20:20:02.000000000 -0500
@@ -247,8 +247,9 @@ void generic_shutdown_super(struct super
/* 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();
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-02-07 14:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-07 14:24 [2.6 patch] More informative message on umount failure Adrian Bunk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome