FC3 automounter fails on mounting iso image via loop device
Herbert Pophal
pophal at zrz.TU-Berlin.DE
Wed Mar 16 10:53:04 UTC 2005
Hi,
after changing from RH7.3 to FC3, the following automount construct
doesn't work any longer:
/etc/auto.master:
/misc /etc/auto.misc --timeout 60
/mnt/loop /etc/auto.loop --timeout 60
/etc/auto.misc:
linux -ro,soft,intr software:/usr/server/software/linux
/etc/auto.loop:
iso -fstype=iso9660,loop,ro :/misc/linux/path/to/image.iso
After the command 'cd /mnt/loop/iso' I will find following message twice
in /var/log/messages:
>> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
>> or too many mounted file systems
>> (could this be the IDE device where you in fact use
>> ide-scsi so that sr0 or sda or so is needed?)
The /misc/linux dir is mounted then. According to a strace, the autofs
executes following mount command:
/bin/mount -t iso9660 -s -o loop,ro,soft,intr
/misc/linux/path/to/image.iso /mnt/loop/iso
(of course, on one line)
Why does the automounter generate the options "soft,intr", and why does
"mount" not tolerate these even with the -s option set? A manual mount
using these options produced the same error, without them it acted as
expected.
Kernel 2.6.10-1.770_FC3, autofs-4.1.3-28, util-linux-2.12a-16.
With RH7.3, kernel 2.4.20-28.7, this worked fine, despite the fact that
the auto.loop table contained the bogus options soft,intr (dunno how
these got there). Kernel 2.4.20-37.7 refused to mount because it didn't
know the loop device until _manually_ loading the kernel module.
Any hints?
hp
More information about the fedora-list
mailing list