Bug 141826

Summary: cdrecord fails on second CD writing attempt
Product: [Fedora] Fedora Reporter: Mikkel Lauritsen <renard>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED CANTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: pfrields, 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-10-03 00:09:58 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 Mikkel Lauritsen 2004-12-03 22:35:36 UTC
When burning CD's using nautilus/cdrecord only the first CD is usable.
All other CD's burned are unreadable - or to be more precise nautilius
sees them as empty but cdrecord is incapable of writing them.

When I try to burn a CD directly from cdrecord it hangs in state DL+
(uninterruptible sleep).

This is apparently the same problem as discussed on
http://www.livejournal.com/community/debian/186598.html , and it might
be related to bug 137049 and bug 141082.


Default FC3 install with all current updates - kernel-2.6.1-1.681,
cdrecord-2.01.1-5


Steps to Reproduce:
1. Boot the PC.
2. Burn a CD from an image.
3a. Burn another CD. The result is a coaster.
3b. Burn a CD using cdrecord. It hangs in state DL+ .


Partial output from cdrecord -scanbus:

scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version
(schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c       
1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus1:
        1,0,0   100) 'LITE-ON ' 'LTR-48125W      ' 'VS04' Removable CD-ROM

Comment 1 Dave Jones 2005-07-15 17:39:58 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 2 Dave Jones 2005-10-03 00:09:58 UTC
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.

There are a large number of inactive bugs in the database, and this is the only
way to purge them.

Thank you.