From: Maciek Nowacki <maciek@Voyager.powersurfr.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Busy on BLKFLSBUF w/initrd
Date: Wed, 23 May 2001 16:11:49 -0600 [thread overview]
Message-ID: <20010523161149.A701@Voyager.powersurfr.com> (raw)
In-Reply-To: <20010523154843.A32583@Voyager.powersurfr.com> <Pine.GSO.4.21.0105231753270.20269-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105231753270.20269-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Wed, May 23, 2001 at 06:05:52PM -0400
On Wed, May 23, 2001 at 06:05:52PM -0400, Alexander Viro wrote:
>
>
> On Wed, 23 May 2001, Maciek Nowacki wrote:
>
> > May 22 09:14:31 wintermute kernel: RAMDISK: romfs filesystem found at block 0
> > May 22 09:14:31 wintermute kernel: RAMDISK: Loading 28216 blocks [1 disk] into ram disk... done.
> > May 22 09:14:31 wintermute kernel: Freeing initrd memory: 28216k freed
> > May 22 09:14:31 wintermute kernel: VFS: Mounted root (romfs filesystem) readonly.
> > May 22 09:14:31 wintermute kernel: Mounted devfs on /dev
> > May 22 09:14:31 wintermute kernel: VFS: Mounted root (romfs filesystem) readonly.
> > May 22 09:14:31 wintermute kernel: change_root: old root has d_count=7
> > May 22 09:14:31 wintermute kernel: Mounted devfs on /dev
> > May 22 09:14:31 wintermute kernel: Trying to unmount old root ... okay
>
> At that point /dev/ram0 _is_ killed.
Really? Because I can still mount it later on without any trouble at all..
after init has started. Hmm, I will try later after running the system for a
while to see if the data is still comprehensible.
> > Perhaps they're bumping up the reference count so that it is impossible to
> > free the ramdisk later?
>
> If you want to keep it until later (i.e. want to destiry it by hands)
> mkdir /initrd on your final root and old one will be remounted there.
> Again, "Trying to unmount old root ... okay" means that it already got
> an equivalent of BKLFLSBUF
Ah, okay.. I assumed this behavior had been removed. I will try this as well.
Maciek
next prev parent reply other threads:[~2001-05-23 22:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 21:48 Busy on BLKFLSBUF w/initrd Maciek Nowacki
2001-05-23 22:05 ` Alexander Viro
2001-05-23 22:11 ` Maciek Nowacki [this message]
2001-05-23 22:21 ` Alexander Viro
2001-05-23 23:23 ` Maciek Nowacki
2001-05-23 23:28 ` Alexander Viro
2001-05-23 23:45 ` Maciek Nowacki
2001-05-24 5:32 ` Mike Galbraith
2001-05-24 10:42 ` Alexander Viro
2001-05-24 10:56 ` Mike Galbraith
2001-05-24 11:24 ` Alexander Viro
2001-05-24 11:57 ` Herbert Xu
2001-05-24 13:27 ` Mike Galbraith
2001-05-24 13:33 ` Alexander Viro
2001-05-24 18:39 ` Maciek Nowacki
2001-05-25 5:20 ` Scott Murray
2001-05-25 15:42 ` Maciek Nowacki
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=20010523161149.A701@Voyager.powersurfr.com \
--to=maciek@voyager.powersurfr.com \
--cc=linux-kernel@vger.kernel.org \
--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.