Bug 9491

Summary:	loop device not freed after umount
Product:	[Retired] Red Hat Linux	Reporter:	Vlado Potisk <reg.bugs>
Component:	kernel	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.0	CC:	bcrl
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-10-05 14:28:43 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 Vlado Potisk 2000-02-16 19:57:23 UTC

I use a file as a filesystem volume using the loop device,
the fstab entry looks like this:
	<myfile> <mountpoint> ext2 loop,user,noauto 0 0

I mount/umount this volume frequently as an ordinary user.
I noticed that after umount, the corresponding device /dev/loop0,
loop1, loop2, etc. gets not freed; after several umounts no loop
devices are left available and mount command fails. To correct it
I had to run losetup -d.

When root umounts the volume, everything looks fine.
The kernel is ver 2.2.11.

Comment 1 Bernhard Rosenkraenzer 2000-08-09 15:17:26 UTC

Looks like a kernel problem, probably fixed by now...

Comment 2 Ben LaHaise 2000-10-04 22:04:16 UTC

Does this still happen in RH7?

Comment 3 Vlado Potisk 2000-10-05 14:28:19 UTC

Don't know and cannot check version 7.0, but
6.2 with kernel 2.2.16 appears to have this bug
corrected.