Control: tags -1 + confirmed
Hello!
I can confirm the described behaviour.
I can reproduce it the official debian kernel.
ii linux-image-3.14-1-amd64 3.14.7-1 amd64 Linux 3.14 for 64-bit PCs
The problem manifests when assigning a loop device explicitly.
ie. mount -v -o loop=/dev/loop4 test.iso /mnt
There is no problem when letting mount automatically detect which
loop device to use.
ie. mount -v -o loop test.iso /mnt
Please note that the previously discussed failing mount() call
("Permission denied") might be a wild goose chase, because even
on a successful mount the first mount() call will fail the same
way (atleast for me):
$ sudo strace mount -v -o loop
~/Downloads/debian-jessie-DI-a1-amd64-netinst.iso /mnt 2>&1 | grep '^mount."'
mount("/dev/loop0", "/mnt", "iso9660", MS_MGC_VAL, NULL) = -1 EACCES
(Permission denied)
mount("/dev/loop1", "/mnt", "iso9660", MS_MGC_VAL|MS_RDONLY, NULL) = 0
$ sudo umount /mnt
$
I see no big reason to investigate this much further though.
It is much better to not explicitly specify the device and just let
the loop device be automatically assigned.
Even specifying "-o loop" is unneccesary. You can just "mount test.img /mnt".
This is all documented in the manpage already! Unfortunately all of it,
in chronological order... so you actually have to read the entire chapter
to the bitter end to find out all the information it contains can just
be ignored and no options should be explicitly specified. :P
So to sum up, just drop all deprecated parameters and simply:
mount file.img /mnt
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
