More informative message on umount failure.
PATCH 1/1 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 <[email protected]>
Signed-off-by Adrian Bunk <[email protected]>
---
This patch was sent by Dave Jones on:
- 2 Feb 2006
fs/super.c renamed from fs/super.c~ +3 -2
@@ -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 ();