Bug 46816

Summary:	Loopback flaky in 2.4.3-12
Product:	[Retired] Red Hat Linux	Reporter:	Ed McKenzie <eem12>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.1	CC:	barryn, chris
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:	2004-09-30 15:39:03 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 Ed McKenzie 2001-07-01 06:40:32 UTC

Copying large numbers of files over loopback from an ISO to the filesystem
(in Nautilus) causes intermittent I/O errors.  Clicking "retry" seems to
let the copy continue, and the data seems to be okay.

I've seen this outside Nautilus as well.

Comment 1 Need Real Name 2001-10-17 23:20:54 UTC

There is a bug reported on kernel traffic with loopback filesystems that causes
hangs where you cannot shutdown or kill the process. It is reportedly fixed in
2.4.3, however I am seeing a problem in doing a cp of a large number of files
(the whole install of 7.1 from non-raid to a raid disk) where it hangs after a
while and I am unable to kill the process or shutdown. As this is the only
similar bug listed here in the RH bugzilla I decided to add to this bug report
rather than create a separate bug

Comment 2 Barry K. Nathan 2004-07-15 08:16:11 UTC

This was fixed quite a while back (although I don't remember the exact
details). I would be completely stunned if this is still present in
Fedora Core or Red Hat Enterprise Linux (in fact I probably would have
noticed by now if it was). This bug should be CLOSED/CURRENTRELEASE.

Comment 3 Bugzilla owner 2004-09-30 15:39:03 UTC

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/