All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Strange umount problem in latest 2.4.0 kernels
Date: Thu, 11 Jan 2001 15:04:56 -0800	[thread overview]
Message-ID: <3A5E3C18.18A6A42@linux.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0101111337250.17363-100000@weyl.math.psu.edu> <3A5E0886.4389692E@Hell.WH8.TU-Dresden.De> <3A5E1E0D.B420A045@Hell.WH8.TU-Dresden.De>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

"Udo A. Steinberg" wrote:

> "Udo A. Steinberg" wrote:
> >
> > The very strange stuff is umount at reboot:
> >
> > umount: none busy - remounted read-only
> > umount: /: device is busy
> > Remounting root-filesystem read-only
> > mount: / is busy
> > Rebooting.

Are you using devfs and do kernel threads have /dev/initctl open?

# lsof /dev
COMMAND     PID USER   FD   TYPE DEVICE SIZE NODE NAME
init          1 root   10u  FIFO    0,5       574 /dev/initctl
keventd       2 root   10u  FIFO    0,5       574 /dev/initctl
kapm-idle     3 root   10u  FIFO    0,5       574 /dev/initctl
kswapd        4 root   10u  FIFO    0,5       574 /dev/initctl
kreclaimd     5 root   10u  FIFO    0,5       574 /dev/initctl
bdflush       6 root   10u  FIFO    0,5       574 /dev/initctl
kupdate       7 root   10u  FIFO    0,5       574 /dev/initctl
i2oevtd       8 root   10u  FIFO    0,5       574 /dev/initctl
i2oblock      9 root   10u  FIFO    0,5       574 /dev/initctl
khubd        12 root   10u  FIFO    0,5       574 /dev/initctl
khttpd       16 root   10u  FIFO    0,5       574 /dev/initctl

-d


[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 274 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;;;;;
version:2.1
email;internet:david@blue-labs.org
title:Blue Labs Developer
note;quoted-printable:GPG key: http://www.blue-labs.org/david@nifty.key=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

  parent reply	other threads:[~2001-01-11 23:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 18:22 Strange umount problem in latest 2.4.0 kernels Udo A. Steinberg
2001-01-11 18:33 ` Daniel Phillips
2001-01-11 18:41   ` Alexander Viro
2001-01-11 19:24     ` Udo A. Steinberg
2001-01-11 19:32       ` Alexander Viro
2001-01-11 20:26         ` Udo A. Steinberg
2001-01-11 20:56       ` Udo A. Steinberg
2001-01-11 21:34         ` Alan Cox
2001-01-11 23:04         ` David Ford [this message]
2001-01-11 21:42       ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11 22:34 Andries.Brouwer
2001-01-11 22:46 ` Udo A. Steinberg
2001-01-11 23:23 ` J . A . Magallon
2001-01-12  8:05   ` Christoph Rohland

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=3A5E3C18.18A6A42@linux.com \
    --to=david@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sorisor@Hell.WH8.TU-Dresden.De \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.