2.4.17: LOOP_SET_FS: Invalid argument

2.4.17: LOOP_SET_FS: Invalid argument

[Olivier Kaloudoff]

Hi gurus,


	I'm simply trying to mount a filesystem
located in a file, and get in trouble with this
message I don't understand...

[root@www root]# dd if=/dev/zero of=/tmp/test bs=1024k count=10
10+0 enregistrements lus.
10+0 enregistrements écrits.

[root@www root]# ls -lh /tmp/test 
-rw-r--r--    1 root     root          10M fév 15 15:00 /tmp/test

[root@www root]# dd if=/dev/zero of=/tmp/test bs=1024k count=10
10+0 enregistrements lus.
10+0 enregistrements écrits.

[root@www root]# mkfs /tmp/test 
mke2fs 1.25 (20-Sep-2001)
/tmp/test is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
2560 inodes, 10240 blocks
512 blocks (5.00%) reserved for the super user
First data block=1
2 block groups
8192 blocks per group, 8192 fragments per group
1280 inodes per group
Superblock backups stored on blocks: 
        8193

Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

[root@www root]# mount /tmp/test /mnt/test/
mount : /tmp/test n'est pas un périphérique de bloc (essayez `-o loop' ?).

[root@www root]# mount /tmp/test /mnt/test/ -o loop
ioctl: LOOP_SET_FD: Invalid argument

[root@www root]# mount /tmp/test /mnt/test/ -o loop -t ext2
ioctl: LOOP_SET_FD: Invalid argument

[root@www root]# mount /tmp/test /mnt/test/ -o loop -t ext3
ioctl: LOOP_SET_FD: Invalid argument

[root@www root]# cat /proc/filesystems  | grep ext 
        ext2
        ext3

[root@www root]# uname -a
Linux www.kalou.net 2.4.17-16mdk #1 Fri Feb 8 16:00:03 CET 2002 i686 unknown


Best Regards,

Kalou

Re: 2.4.17: LOOP_SET_FS: Invalid argument

[Andreas Schwab]

Olivier Kaloudoff <kalou@kalou.net> writes:

|> Hi gurus,
|> 
|> 
|> 	I'm simply trying to mount a filesystem
|> located in a file, and get in trouble with this
|> message I don't understand...

Perhaps /tmp is mounted as tmpfs?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."