mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Haumer <andreas@xss.co.at>
To: Tobias Reinhard <T.Reinhard@losekann.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem unmounting initrd-romfs in 2.4.21
Date: Fri, 20 Jun 2003 16:47:35 +0200	[thread overview]
Message-ID: <3EF31E87.6050804@xss.co.at> (raw)
In-Reply-To: <BDB86409B697CB4DBB8A5BF487B9D61A3933@srv01.losekann.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Tobias Reinhard wrote:
> Hi all!
>
> I'm booting up with a initrd in a romfs. After loading all needed
> modules and pivoting root I unmount the initrd and flush the used
> buffers.
>
> Since I updated to 2.4.21 I can't unmount the initrd - it says it's
> busy, but it's no (or at least lsof does say so).
>
> I use kernel 2.4.21 with /drivers/Makefile , /drivers/ide and
> /include/linux/ide.h from ac1 to reenable ide-modules.
>
> Anyone know the problem?
>
Hm, just a guess: do you have devfs mounted to /dev
on the initial ramdisk (probably automounted by the
kernel, with config option CONFIG_DEVFS_MOUNT=y)?

Check the output of "mount", it'll show you if there's
still something mounted under the "old" root.

We use initrd + devfs for ages now (we even use romfs for
initrd like you do), and it works fine with 2.4.21 too.

HTH

- - andreas

- --
Andreas Haumer                     | mailto:andreas@xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+8x6CxJmyeGcXPhERAs7RAKCWiPn2qnLvI9v6GdVj3djPeBcPvQCeP1X2
Fd/GfnFm7tWiCGpp6A6zO6c=
=V9df
-----END PGP SIGNATURE-----


      reply	other threads:[~2003-06-20 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20  9:41 Tobias Reinhard
2003-06-20 14:47 ` Andreas Haumer [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=3EF31E87.6050804@xss.co.at \
    --to=andreas@xss.co.at \
    --cc=T.Reinhard@losekann.de \
    --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®