Red Hat Bugzilla – Bug 896160
kernel: loop - please do not pre-create devices: CONFIG_BLK_DEV_LOOP_MIN_COUNT=0
Last modified: 2013-12-27 17:44:10 EST
Loop devices can and should be created on-demand, and only when needed, losetup
has been updated since Fedora 17 to do that just fine. Nothing should require
an arbitrary number of pre-created dead and dumb devices, and hope it will
find an unused one in that number.
We should disable it early in Fedora 19 and see if anything still relies on
the I-hope-it-will-work-out facility. If that's the case, we should fix it
In any case, the old behaviour can always be requested with a kernel command
And if there is no specific reason, please als turn loop into a loadable module:
It's not an early-boot or essential functionality, it should be fine to loa dthe module only on-demand, which happens automatically by udev when /dev/loop-control
That way, even a modprobe.d/ config file can specify the number of pre-created
(In reply to comment #0)
> And if there is no specific reason, please als turn loop into a loadable
Oh, that should be:
While at it, maybe we can also disable:
Fedora 18 was the last version of util-linux supporting cryptoloop
devices, it all needs to be done by dmcrypt these days.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Moving this to rawhide. Clearly this missed early F19 :\. I'll try and get to it tomorrow.
OK, I've made all three changes. Hopefully dracut will bring in the loop module if it needs it for anything in the initramfs.
(In reply to Josh Boyer from comment #6)
> OK, I've made all three changes. Hopefully dracut will bring in the loop
> module if it needs it for anything in the initramfs.
yes it does, except for the dracut crypt-loop module, which is not working anyway anymore.
See https://bugzilla.redhat.com/show_bug.cgi?id=993637 .
>In any case, the old behaviour can always be requested with a kernel command
I don't suppose you'd care to mention what the kernel command line option is?
This breaks realcrypt a.k.a truecrypt.
I solved this problem by creating my own loop device because I don't want to change the kernel parameters.
The other method I think it is described in the bug https://bugzilla.redhat.com/show_bug.cgi?id=1019440
Took the script from http://www.tldp.org/HOWTO/CDServer-HOWTO/addloops.html , bottom of the page "3.4. Creating the Loop Devices in /dev"
if [ -b $loop_device ]; then
echo "$loop_device already exists! Exiting!"
sudo mknod -m660 $loop_device b 7 8
sudo chown root:disk $loop_device
sudo chmod 666 $loop_device
truecrypt <container> <mount_point>