Bug 693536

Summary:	How to increase the number of configured loop devices
Product:	[Retired] Fedora Documentation	Reporter:	Alan Pevec <apevec>
Component:	virtualization-guide	Assignee:	Fedora Documentation Project <docs>
Status:	CLOSED WONTFIX	QA Contact:	Nobody's working on this, feel free to take it <nobody>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	jhradile, me, swadeley, zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-31 19:13:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alan Pevec 2011-04-04 22:06:06 UTC

Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html

Number of loop devices cannot be changed via modprobe.conf since loop is not a kernel module anymore:

# grep DEV_LOOP /boot/config-2.6.34.8-68.fc13.x86_64 
CONFIG_BLK_DEV_LOOP=y

Comment 2 Paul W. Frields 2011-04-04 22:52:07 UTC

Shouldn't be needed since 2.6.24 (?) or so.

Comment 3 Alan Pevec 2011-04-05 08:29:08 UTC

(In reply to comment #2)
> Shouldn't be needed since 2.6.24 (?) or so.

But /dev/loop* entries aren't created on demand, are they?
AFAICT you still need to run MAKEDEV to get additional loop device entries.

Comment 4 Karsten Wade 2011-12-14 03:48:55 UTC

Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result!

Comment 5 Pete Travis 2017-08-31 19:13:22 UTC

Hello Alan, thanks for reporting, and apologies for the lack of response.  This is an interesting question, however as you can tell, this guide is no longer actively maintained, so I am closing this issue.