Bug 63412 – builtin losetup -d fails

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 63412 - builtin losetup -d fails

Summary:	builtin losetup -d fails

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	sash (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Karsten Hopp
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-04-13 09:58 EDT by Derek Tattersall
Modified:	2007-04-18 12:41 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-08-24 17:39:12 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Derek Tattersall 2002-04-13 09:58:38 EDT

Description of Problem:
after doing -losetup /dev/loop1 /file
-losetup -d /dev/loop1 fials with 
Error unassociating device: Device or resource busy

Version-Release number of selected component (if applicable):
sash-3.4-11

How Reproducible:
Happens every time.  Have to exit sash to delete the association

Steps to Reproduce:
1. Create a file file in /
2. sash
3. -losetup /dev/loop1 /file
4. -losetup -d /dev/loop1

Actual Results:
Error unassociating device: Device or resource busy

Expected Results:
The file to disassociated from the loop device

Additional Information:

Comment 1 Bill Nottingham 2002-04-14 23:50:25 EDT

Does this succeed with normal losetup?

Comment 2 Derek Tattersall 2002-08-11 16:33:19 EDT

Works fine with standalone losetup.  Also fails in limbo beta4 the same way,
where standalone losetup works as advertised.

Comment 3 Karsten Hopp 2004-08-24 17:39:12 EDT

works in the current version

Note You need to log in before you can comment on or make changes to this bug.