From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre19 oops in try_to_free_pages
Date: Tue, 28 Nov 2000 14:52:29 +0200 [thread overview]
Message-ID: <20001128145229.O53529@niksula.cs.hut.fi> (raw)
In-Reply-To: <20001128134418.C54301@niksula.cs.hut.fi> <E140k8t-0004Sv-00@the-village.bc.nu>
In-Reply-To: <E140k8t-0004Sv-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Nov 28, 2000 at 12:45:49PM +0000
On Tue, Nov 28, 2000 at 12:45:49PM +0000, you [Alan Cox] claimed:
> > BTW: What are those seemingly harmless "VFS: busy inodes on changed
> > media." messages I'm getting tons of?
>
> They are not harmless. Someone forcibly unmounted a disk of some sort
> from a device that was in use, and while that shouldnt have killed the box
> it seems it did
I've got hundreds of those during several weeks, and in different boots.
It seems the kernel starts spitting them right after using cdrom.
I wasn't the one who used cdrom, so it is possible, that the person in
question had been able to eject the cd without unmounting it first. I'll
check if the door locking on that device works.
But you are certain that the oops was eventually caused by these and not
by any bug in vm?
-- v --
v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 11:44 Ville Herva
2000-11-28 12:45 ` Alan Cox
2000-11-28 12:52 ` Ville Herva [this message]
2000-11-28 12:57 ` Alan Cox
2000-11-28 13:09 ` Ville Herva
2000-11-28 13:40 ` Alan Cox
2000-11-29 0:38 ` Andrea Arcangeli
2000-11-29 8:29 ` Ville Herva
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=20001128145229.O53529@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--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®