2.3.40 loop-device-behaviour

[Richard B. Johnson]

On Tue, 25 Jan 2000, Ralf Burger wrote:

> hi all,
> 
> the loop-device in this kernel shows a little bit strange behaviour:
> 
> this script works fine since a long time
> ----------------------------------------------------------------------
> dd if=/dev/zero of=/tmp/fsfile bs=1k count=4000
> mkfs.minix  /tmp/fsfile 4000
> mount -t minix -o loop /tmp/fsfile /mnt/fd2
> ----------------------------------------------------------------------
> 
> but with a 2.3.40-kernel it results in:
> ----------------------------------------------------------------------
> csb:/usr/src/linux # dd if=/dev/zero of=/tmp/fsfile bs=1k count=4000
> 4000+0 records in
> 4000+0 records out
> csb:/usr/src/linux # mkfs.minix  /tmp/fsfile 4000
> 1344 inodes
> 4000 blocks
> Firstdatazone=46 (46)
> Zonesize=1024
> Maxsize=268966912
> 
> csb:/usr/src/linux # mount -t minix -o loop /tmp/fsfile /mnt/fd2
> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
>        or too many mounted file systems
> ----------------------------------------------------------------------
> 
> 
> loop.o is loaded and minix is supported
> 
> lsmod 
> Module                  Size  Used by
> loop                    7280   0 
> 
> mount
> /dev/fd0 on /mnt/fd0 type minix (rw)
> 
> 
> regards
> 
> ralf

I also reported the problem with the loop device. A temporary work
around is to use your ramdisk instead of mounting a file using
the loop device. This is if you are trying to make an initrd or
similar. Remember to zero /dev/ram0 first because mkfs doesn't.


Cheers,
Dick Johnson

Penguin : Linux version 2.3.39 on an i686 machine (800.63 BogoMips).


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