On Sat, Feb 08, 2014 at 10:45:41PM -0500, Phillip Susi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 02/05/2014 05:14 PM, ael wrote: > > The exact behaviour has changed with different kernels. I am > > running on a (locally compiled) 3.14.0-rc1 just now - and with a > > fully updated testing environment. > > > > On this kernel -o loop=/dev/loop0 just gives the message: mount: > > stolen loop=/dev/loop0 (and fails). > > I just ran a freshly built 3.14-rc1 kernel built from vanilla upstream > source and an up to date jessie/testing system and it works fine for > me. What exactly do you mean it fails?
Ok. That is interesting. There must be something peculiar on the (rather old i386) machine on which I test. I am not on that machine just now, but I am am confident that something like mount -o loop=/dev/loop1 file.iso /mountpoint gives the message "stolen loop". Looking at mount or df -h /mountpoint shows nothing mounted. mount -o loop file.iso /mountpoint succeeds. That was on 3.14-rc1. There is no (other) explicit error message as on earlier kernels. Maybe I have something odd in my .config, but that seems unlikely. I believe that I used a loop module parameter to increase the number of loop devices. I will try and remember to check that. I guess that I should experiment with changing max_loop just in case that is triggering a bug. I will be away from the relevant machine for perhaps a month soon, but will try to find to to make the test before I leave. Otherwise there may be some delay... ael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
