From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: More imformative message on umount failure.
Date: Thu, 2 Feb 2006 20:24:05 -0500 [thread overview]
Message-ID: <20060203012405.GA7306@redhat.com> (raw)
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();
reply other threads:[~2006-02-03 1:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060203012405.GA7306@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox