Messages in this thread |  | | Date | Sun, 21 Jul 1996 13:17:48 +0100 (BST) | From | John Storrs <> | Subject | Ramdisk Bug? |
| |
Hi all
Having a few problems with 2.0.8 as a result of trying to rebuild a rescue disk using yard-1.5. The ramdisk driver doesn't seem to work correctly. The last time I did this was with 1.3.80 or so - no problems then. I have a 32Mb pentium system. I built the kernel with the ramdisk and initial ramdisk options enabled. The ramdisk devices /dev/ram[0-7] and /dev/initrd are correct.
After running into problems with yard I turned to ramdisk.txt in linux/ Documentation and attempted to create a ramdisk: dd if=/dev/zero of=/dev/ram1 bs=1k count=2048 This terminates ok, but produces log messages such as kernel: ctor 346 kernel: equest: I/O error, dev 01:01, sector 1302 kernel: equest: I/O error, dev 01:01, sector 2590 Then trying mke2fs -vm0 /dev/ram1 2048 I seem to be able to build a file system on it (though in cycling through this bug search I've had user error messages here sometimes). However mount -t ext2 /dev/ram1 /mnt fails with the user error message mount: wrong fs type or bad superblock on /dev/ram1. Same result with different ramdisk devices and sizes.
Is this a bug or do I have a configuration problem?
John
John Storrs, Laboratory for Micro Enterprise Oakley Court, Benson, Wallingford OX10 6QH, UK tel/fax 01491 832932 email lme@storrs.demon.co.uk home page under construction http://www.i-way.co.uk/~storrs/
|  |