Problems with loop device?

Problems with loop device?

Post by Andrew Telfo » Wed, 09 Oct 1996 04:00:00

 I have tried the loop device on a recent kernel 2.0.20...

        1. Does anyone have a pointer to information on
                using encryption on the loop device.
                There is a version of DES add-ins for the
                kernel somewhere on the net but they
                looked very old.
        2. Should this work on an ncpmounted filesystem.
                Losetup worked but the mke2fs on the
                /dev/loop0 device failed.
Andrew Telford

BHP Research - Melbourne Laboratories  


1. Problem with loop devices and mounting a cdrom


I have a problem mounting (standart) cdroms. When I write
mount -tiso9660 /dev/cdrom /cdrom      (SuSE 6.2 Kernel 2.2.16)
Then linux write the unsual stuff like cd write protected mouted,
that' okay.

when I do a ls -la I get the following line:

-r-xr-xr-x 1 root root 0 Jan 1 1970 cdrom

as you can see cdrom is a file which is 0 byte and you have no acces
to the cdrom.

We also use this server to serve cdrom's. There are serveral cdimages
(created with dd...) and these images are mounted with the loop
command like "mount -tiso9660 -o loop /....". But when I try to mount
more than 18 images it tells me "bad superblock on device /dev/loop19
or too many mounted file systems, wrong fs type, bad option".

The devices are created with mknod b loopX 7 X, the loop.c source has
the linx #define MAX_LOOP 80 and the kernel was rebuild. So everything
should be right.


2. problem with rm?

3. PROBLEM: block loop device hangs

4. New Files Imported

5. PROBLEM: compiling loop device

6. ps/2 mouse difficulty

7. Mount compressed file as a loop device (mount -o loop.. )

8. Grep Question

9. Use Multiple Device Drivers with loop devices?

10. 2.4 loop device over block device broken

11. dependencies problems on loop back device (linux 2.4.14)

12. RH7.2 and loop device has problems and I seek help.

13. cramfs with loop device problem