Messages in this thread Patch in this message | | | Date | Thu, 2 Feb 2006 20:24:05 -0500 | From | Dave Jones <> | Subject | More imformative 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>
--- 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(); - 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/
| |