Hello!
I've tried to mount an ext2 filesystem image (ca. 1GB) stored on a WIN
computer via the loop device under 2.4.22:
(Initially the file scratch2.img is filled with 0s.)
#smbmount //win02/scratch /pro -o username=sambadisk,workgroup=MYDOMAIN
#losetup /dev/loop0 /pro/scratch2.img
#mke2fs /dev/loop0
#mount /dev/loop0 /scratch -t ext2
#cp -r linux-2.4.22 /scratch
cp: cannot create directory `/scratch/linux-2.4.22/drivers/video/sis':
Input/output error
cp: cannot create directory `/scratch/linux-2.4.22/drivers/video/aty':
Input/output error
etc.
#dmesg
EXT2-fs error (device loop(7,0)): read_inode_bitmap: Cannot read inode
bitmap -
block_group = 4, inode_bitmap = 131073
EXT2-fs error (device loop(7,0)): read_block_bitmap: Cannot read block
bitmap -
block_group = 4, block_bitmap = 131072
With 'mount /dev/loop0 /scratch -t ext2 -o sync':
#mkdir somedir
mkdir: cannot create directory `somedir': Input/output error
#dmesg
IO error syncing ext2 inode [loop(7,0):0001e6cf]
IO error syncing ext2 inode [loop(7,0):0001e6cf]
I've found a similar problem in the kernel archives with the topic 'Loop
devices under NTFS' (Aug 27-28 2002) There was mentioned a patch for
2.5.31 to fix this problem. Hasn't been it applied to stable versions
since then? Is there a patch for current versions?
Thanks
------------------------
Gabor Kovacs, PhD student
Eotvos University, Budapest, Hungary
Kovacs Gabor wrote:
> I've tried to mount an ext2 filesystem image (ca. 1GB) stored on a WIN
> computer via the loop device under 2.4.22:
>
> (Initially the file scratch2.img is filled with 0s.)
>
> #smbmount //win02/scratch /pro -o username=sambadisk,workgroup=MYDOMAIN
> #losetup /dev/loop0 /pro/scratch2.img
> #mke2fs /dev/loop0
> #mount /dev/loop0 /scratch -t ext2
>
> #cp -r linux-2.4.22 /scratch
> cp: cannot create directory `/scratch/linux-2.4.22/drivers/video/sis':
> Input/output error
> cp: cannot create directory `/scratch/linux-2.4.22/drivers/video/aty':
> Input/output error
This bug should be fixed in loop-AES version of loop, here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v1.7e.tar.bz2
Can you try again with that version?
Regards,
Jari Ruusu <[email protected]>
On Fri, 2003-09-19 at 17:24, Jari Ruusu wrote:
>
> This bug should be fixed in loop-AES version of loop, here:
>
> http://loop-aes.sourceforge.net/loop-AES/loop-AES-v1.7e.tar.bz2
>
> Can you try again with that version?
It works! (2.4.22 + loop-AES-v1.7e.tar.bz2)
Thanks!
Gabor Kovacs