Bug 1024366 - losetup does not use loop-control to add device
Summary: losetup does not use loop-control to add device
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Juraj Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-29 14:11 UTC by Petr Beňas
Modified: 2015-09-01 03:39 UTC (History)
2 users (show)

Fixed In Version: util-linux-2.23.2-7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:54:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Petr Beňas 2013-10-29 14:11:23 UTC 
Description of problem:
RHEL7 is built with 
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=0
so there are no loopback files by default. Loopback file can by used by  
# mount -o loop file mountpoint
but losetup cannot be used. 

Version-Release number of selected component (if applicable):
util-linux-2.23.2-6.el7.x86_64
kernel-3.10.0-37.el7.x86_64
kernel-3.10.0-33.el7.x86_64

Actual results:
losetup /dev/loopX file does not work

Expected results:
Losetup creates the /devl/loopX file using the loop-control interface if the loopback file does not exist yet. 

Additional info:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=770fe30a46a12b6fb6b63fbe1737654d28e84844
Comment 2 Karel Zak 2013-11-01 08:51:14 UTC 
Fixed by upstream commit 3cb2413b02ff01f535b82eb630bd4f157ed7b1c8 (v2.24).
Comment 6 Ludek Smid 2014-06-13 09:54:52 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.