public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: remco@solbors.no (Remco B. Brink)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 kernel mount crash
Date: 08 Mar 2001 15:41:12 +0100	[thread overview]
Message-ID: <m366hkuxvb.fsf@localhost.localdomain> (raw)
In-Reply-To: <E14b1Nh-000321-00@the-village.bc.nu>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> > I used kgcc to compile the kernel, did not get any of the RH7 gcc warning messages
> > and still am left with a not-so-stable mount.
> 
> Its certainly worth building with kgcc as well to make sure, and in this case
> it looks like the problem is really in the kernel proper

Actually the mount process behaves in exactly the same way as my emacs process
as mentioned in an earlier post (topic: "process with connection in CLOSE_WAIT won't 
die in 2.4.2").

It'll stay in the proceslist regardless of what kill signal is sent to it
and appears to be (and very much _stay_) in un-interuptable sleep.

The same can be said for the various mount processes, both when mounting
loopback and scsi devices.

Another thing that struck me as weird was that after all the problems
with the mount and emacs process, trying to unmount a NFS share was not
possible even though the NFS server had no problems whatsoever mounting
new shares.

regards,
Remco

-- 
Remco B. Brink                                  Norge-iNvest AS
Kung foo                            http://www.norge-invest.com
        PGP/GnuPG key at http://remco.xgov.net/rbb.pgp

In most countries selling harmful things like drugs is punishable.
Then howcome people can sell Microsoft software and go unpunished?
(By hasku@rost.abo.fi, Hasse Skrifvars)

      reply	other threads:[~2001-03-08 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 14:03 2.4.2 kernel mount crash Jie Zhou
2001-03-08 14:13 ` Remco B. Brink
2001-03-08 14:27   ` Alan Cox
2001-03-08 14:41     ` Remco B. Brink [this message]

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=m366hkuxvb.fsf@localhost.localdomain \
    --to=remco@solbors.no \
    --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