Bug 101997
Summary: | max_loop should be set higher for mounting loopback devices | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brian "netdragon" Bober <netdragon> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | barryn |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:41:25 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
Brian "netdragon" Bober
2003-08-08 18:53:29 UTC
This is the error I get: mount: could not find any free loop device *** Bug 102000 has been marked as a duplicate of this bug. *** I realize you can do: rmmod loop modprobe loop max_loop=255 But wouldn't it be nice if we didn't have to deal with this (and the uncertainty that if other people try to do what you do they won't have loop as a separate module) by increasint it to some reasonable number like 16? Is there a reason its 8? This seems like a request to have the kernel change the default number of max_loop to 16. 16, or 256, whatever number would be reasonable as a default. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |