On Friday 21 Mar 2003 1:29 pm, Tom Brinkman wrote: > On Thursday March 20 2003 05:16 pm, Richard Urwin wrote: > > I have just had exactly the same problem. Wrote a CDRW in GCombust, > > finished OK, wouldn't eject the CD. > > > > lsof reported that nothing on the cd was open. ie "lsof|grep > > cdrom2" and "lsof|grep scd0" both reported nothing. > > > > Seeing that nothing was open I unmounted it with "umount -l > > /mnt/cdrom2" and that at least gave me my cd back. Everything > > appeared fairly sane I think. The jury is still out as to whether I > > can burn another CD following this one, and I'm no expert about > > what I might have broken with that unmount. > > > > I did have supermount enabled. > > CDr's are not mounted for burning. So 'umount' isn't part of the > equation.
I did open the CD in Konquerer immediately after the burn, just to make sure the data was there. This time through I closed GCombust first. (And closed konquerer before trying to eject, of course.) > It's likely just coincidental that by the time you ran that > command, whatever has holding on to the burner had released it. Next > time try 'eject /dev/scd0' (or scd? depending on which ? your burner > is). 'Course if you're burning as root (you shouldn't be) you'll need > to run the eject command as root. $ eject /dev/scd0 # Came out, went back in again $ sudo umount -l /mnt/cdrom2 Password: $ eject /dev/scd0 # Came out, stayed out While I grant that that sequence took thirty seconds or so, and things may have changed between the two ejects, that was a lot less time than I took fiddling with it last night. It stands to reason that the burner must lock the drive closed while the burn is happening. I don't know how that happens. Even if it isn't a mount it might still have a similar effect on the top level mount/umount/eject functionality. > Supermount has been vastly improved in 9.1. Specially if you use > the premptable, low latency kernel found in contribs (2.4.21-0.16mm). > OTOH, supermount isn't involved in this problem since CDr's are not > mounted for burning anyway. The reason I'm doing this is to archive off my files so when I load 9.1, hopefully next week, I can nuke and pave, and this time get the partitions right so I don't have to do it next time. Not that a few backups now and then aren't a good thing ;-) -- Richard Urwin
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
