From: Nikolai Bulkin <nick@emcraft.ru>
To: linux-kernel@vger.kernel.org
Subject: Busy inodes after unmount
Date: Fri, 21 Sep 2001 19:06:33 +0400 [thread overview]
Message-ID: <01092119063300.01004@iron.auriga.ru> (raw)
Hi All,
I'm getting the "Busy inodes after unmount. Self-destruct in 5 seconds. Have
a nice day..." message when trying to unmount initrd. It gets unmounted
alright but the message is frightening.
The error message appears only if I've written something to a ramdisk (not
initrd, to another one). For instance, the following commands in /linuxrc are
enough to get the message:
#!/bin/ash
dd if=/dev/zero of=/dev/ram6 count=1
exit
The real root file system is on a SCSI disk.
I've tried it with the 2.4.3, 2.4.9, 2.4.10-pre11 kernels - with the same
results. Also, I added printouts to the fs/inode.c file (from one of the
patches sent via this list some while ago) showing what inodes appear busy.
It's a single unnamed inode, number 54, i_count equals to 1 and zero i_state.
Does anyone have any idea as to why this may happen and how to fix this?
Thanks,
Nick
reply other threads:[~2001-09-21 15:06 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=01092119063300.01004@iron.auriga.ru \
--to=nick@emcraft.ru \
--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
all inboxes | Powered by JetHome®