lkml.org 
[lkml]   [2000]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.3.40 loop-device-behaviour
Date
> 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

I do not know if your problem is the same, but I experience
difficulties with stale data staying in memory.

Consider the following script:

genromfs -a 512 -f flash.root.image -d proto
mount -t romfs -o ro,loop=/dev/loop0 flash.root.image /mnt
silo -C /mnt/etc/silo.conf -J flash.total -i /mnt/boot/ieee32 \
-b /mnt/boot/second.b
umount /mnt

It works only once. On the second time silo gets stale data.
My workaround is to add "cat /wad/mp3/*.mp3 > /dev/null"
right before the mount.

I talked to Alan and he says that somebody needs to do
ioctl(fd, BLKFLSBUF), presumably losetup. I have not tested
his suggestion yet.

--Pete

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

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.041 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site