On Wednesday 18 June 2008, Michael Schwendt wrote: >On Wed, 18 Jun 2008 11:07:45 -0400, Gene Heskett wrote: >> That is because the verify phase of k3b will not wait till the drive has >> recognized the disk after the eject cycle, so it errors out. I have >> squawked about that on the k3b bz, to no avail. > >Unfortunately, there are multiple issues. One is related to ejecting and >closing the tray prior to verification. That breaks differently. In k3b bz >I suspect there are multiple problem reports and duplicates, too. The >ticket I've linked within Red Hat bz (440343 -> 444344) is: >http://bugs.kde.org/show_bug.cgi?id=157186 > And that one doesn't quite waddle like this duck, particularly when you put that spin on it. Mine opens and closes the drawer just fine, but only waits about 3 or 4 seconds before giving up. Anne suggested setting it so it doesn't eject, but then the drive generally has no clue about how to access the disk, so that fails also. The drive itself must read the equ of LSN0 from the disk, deduce the file system and configure itself, all the while poking at the disk to see what it really is. This process, on any drive I've ever owned, can take upwards of 75 seconds, and rarely less that 55. Generally, if during the time that the drive led is still on after the disk has been pulled back in, then k3b, or anything else that wants to read it can sit by silently, or take a dump and abort the operation. k3b, or whatever util is doing this latter, and really does need to learn to wait. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) There are no great men, only great challenges that ordinary men are forced by circumstances to meet. -- Admiral William Halsey -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
