On Wednesday 14 March 2007 01:58, Eduard Bloch wrote: > > This just does not add up. The only difference is IMO the driver used by > /dev/sgX vs. /dev/sr0 (sg vs. sg_io). sg_io works pretty well, while sg > does weird things: after few data writes it starts returning false sense > codes indicating that the drive is busy (04/08, long drive in progress). > So wodim keeps retrying, which is the correct way to do in order to not > come to late. And after few dozens of retry it returns weird stuff and > the process breaks. >
This seems to be the same problem as here: https://bugzilla.novell.com/show_bug.cgi?id=226019 There is no shared lock between sg and sr, some other program (HAL) accesses the device in parallel and LG burners don't like it. -- Vladimir Nadvornik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
