On Fri, Jul 11, 2014 at 1:35 PM, Michael Biebl <bi...@debian.org> wrote: > Am 11.07.2014 05:01, schrieb Kay Sievers: >> The logic in util-linux, libmount, losetup, ... tries to access >> /dev/loop-control which will block and trigger a kernel-side module >> auto-load. >> >> All that is needed is that tmpfiles have created the "dead" device >> node to access from userspace, and the major/minor of that node will >> resolve to the kernel module providing the requested device. > > This seems to be setup correctly afaics: > > # modinfo loop > filename: /lib/modules/3.14-1-amd64/kernel/drivers/block/loop.ko > alias: devname:loop-control > alias: char-major-10-237 > alias: block-major-7-* > license: GPL > depends: > intree: Y > vermagic: 3.14-1-amd64 SMP mod_unload modversions > parm: max_loop:Maximum number of loop devices (int) > parm: max_part:Maximum number of partitions per loop device (int) > > # ls -la /dev/loop* > crw------- 1 root root 10, 237 Jul 11 06:02 /dev/loop-control > > > Yet, mount still fails > # mount -oloop /tmp/ISO/boot.iso /mnt/loop/ > mount: Could not find any loop device. Maybe this kernel does not know > about the loop device? (If so, recompile or `modprobe loop'.) > > Is our mount version too old or should it work irregardless of the mount > version? > > # mount --version > mount from util-linux 2.20.1 (with libblkid and selinux support)
# lsmod | grep loop # mount -o loop nothing /mnt mount: nothing: failed to setup loop device: No such file or directory # lsmod | grep loop loop 28197 0 # mount --version mount from util-linux 2.25-rc2 (libmount 2.25.0: selinux, assert, debug) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
