Bug 57290

Summary:	you can delete loop devices that it are mount
Product:	[Retired] Red Hat Linux	Reporter:	acount closed by user <a1459440>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-12-16 22:47:34 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 acount closed by user 2001-12-08 22:57:25 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.16-0.5 i686)

Description of problem:


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


How reproducible:
Always

Steps to Reproduce:
1. mount -o loop my.iso /mnt/iso
2. rm my.iso
3. is it  a bug ? or must be the kernel put chattr i to the iso file 
	

Additional info:

Comment 1 Tethys 2002-01-05 00:06:45 UTC

IMHO, this isn't a bug. It's the way Unix has always worked. You can delete
any file that's open, whether it's being viewed with less, or mounted as a
loopback filesystem. The kernel will hang onto the resources until it's
closed. The only bug is in fuser, which doesn't tell you that a file is in
use as a loopback filesystem (or at least, it didn't last time I checked).

Comment 2 acount closed by user 2003-06-08 16:10:52 UTC

in redhat_9 it happen too