Messages in this thread | | | From | "H. Peter Anvin" <> | Date | 14 Apr 2001 23:36:59 -0700 |
| |
Hello friends,
I am trying the following setup, and it works beautifully, *except* that I don't seem to be able to free the ramdisk memory at the end. This is using the 2.4.3 stock kernel:
I load an initrd in "non-initrd" mode:
label single kernel vmlinuz append initrd=initrd.gz root=/dev/ram0 init=/linuxrc single
The initrd sets up a ramfs which is intended to become the root filesystem, and then calls pivot_root:
[....] umount /proc
# At this point, all that is mounted is /ram and /ram/usr
# Switch roots and run init cd /ram pivot_root /ram /ram/initrd exec /sbin/init "$@"
(And yes, the /ram/initrd mount point directory does exist.)
This successfully runs init, and I can umount /initrd in the new setup, but I cannot then destroy the ramdisk contents by calling ioctl([/dev/ram0], BLKFLSBUF, 0) -- it always returns EBUSY. What is holding this ramdisk busy, especially since I could successfully umount the filesystem? Seems like a bug to me.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/
| |