From: Kovacs Gabor <kgabor@BOLYAI1.ELTE.HU>
To: linux-kernel@vger.kernel.org
Subject: Loop device and smbmount: I/O error
Date: 18 Sep 2003 21:45:56 +0200 [thread overview]
Message-ID: <1063914356.1639.34.camel@warp> (raw)
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
next reply other threads:[~2003-09-18 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 19:45 Kovacs Gabor [this message]
2003-09-19 15:24 ` Loop device and smbmount: I/O error Jari Ruusu
2003-09-21 16:46 ` Kovacs Gabor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1063914356.1639.34.camel@warp \
--to=kgabor@bolyai1.elte.hu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.