Hi Maurice :)
>Also, later on I learned that one must "cd" into the mounted ramdisk
>to cause the corruption.
I've reproduced all your steps and my ramdisk didn't get
corrupted. See below.
>I do the following to setup a ram disk on /dev/ram0...
>dd if=/dev/zero of=/dev/ram0 bs=1k count=4096
>mkfs.ext2 /dev/ram0 -m 0 -N 4096
Identical commands issued...
>I mount it and already the lost+found directory is not there.
Mine is OK. The lost+found is there. I don't suffer any of the
other problems you tell, neither.
Maybe you have bad ram chips, or a damaged mke2fs (unlikely), but
the kernel seems to work OK. I've tested with 2.4.18 and 2.4.17.
Raśl
-
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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:31 EST