Re: Busy on BLKFLSBUF w/initrd

Alexander Viro (viro@math.psu.edu)
Wed, 23 May 2001 18:05:52 -0400 (EDT)


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.

> 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

I wonder why does it get -EBUSY if you repeat it... Uh-oh...

Folks, who the hell is responsible for rd_inodes[] idiocy?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/