Bug 163662

Summary:	Mounting a blank CDRW causes system to hang
Product:	[Fedora] Fedora	Reporter:	Peter Cook <p.cook>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4	CC:	robatino, wtogami
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:	2005-07-20 21:24:53 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 Peter Cook 2005-07-20 02:06:10 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
I inserted a blank CDRW then typed:

mount /dev/cdrom /media/cdrecorder

Then the system hung.

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


How reproducible:
Always

Steps to Reproduce:
1.Insert blank CDRW
2.In terminal type: mount /dev/cdrom /media/cdrecorder

  

Actual Results:  The system hangs and I must hard reboot.

Expected Results:  Warning message should appear that blank CDRW can't be mounted.

Additional info:

I know it doesn't make sense to mount a blank CD however I stumbled across this bug by accident while using the usermount GUI (System Tools - Disk Management...same results as using mount command) and trying to copy a CD. Unfortunately the accident caused me to reboot. I shouldn't have to reboot.

Comment 1 Peter Cook 2005-07-20 02:09:35 UTC

I noticed that when I was asked to initially choose a component the instructions
said that if the component you were reporting a bug on was not in the list to
choose the closet component and add some comments to the description field. I
added comments to explain that "diskcheck" was not the correct component, but I
don't see those comments anywhere in this bug report. ???

Comment 2 Andre Robatino 2005-07-20 13:30:41 UTC

  Which kernel are you using?  This bug was considered fixed with the latest
2.6.12-1.1398_FC4 kernel.

Comment 3 Peter Cook 2005-07-20 21:24:53 UTC

I was using 2.6.12-1.1390, but I upgraded to 1398 and the problem is resolved.
Thanks!