From owner-freebsd-bugs@FreeBSD.ORG Sun Dec 21 14:20:52 2008 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF9DC1065692 for ; Sun, 21 Dec 2008 14:20:52 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh04.mail.saunalahti.fi (emh04.mail.saunalahti.fi [62.142.5.110]) by mx1.freebsd.org (Postfix) with ESMTP id 6AFA18FC21 for ; Sun, 21 Dec 2008 14:20:52 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-11.mail.saunalahti.fi [62.142.5.95]) by emh04-2.mail.saunalahti.fi (Postfix) with SMTP id D1AA913B3BA; Sun, 21 Dec 2008 16:02:37 +0200 (EET) Received: from emh07.mail.saunalahti.fi ([62.142.5.117]) by vs3-11.mail.saunalahti.fi ([62.142.5.95]) with SMTP (gateway) id A05002CBFF3; Sun, 21 Dec 2008 16:02:37 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh07.mail.saunalahti.fi (Postfix) with SMTP id 75F741C638F; Sun, 21 Dec 2008 16:02:35 +0200 (EET) Date: Sun, 21 Dec 2008 16:02:35 +0200 From: Jaakko Heinonen To: Garrett Cooper Message-ID: <20081221140235.GC806@a91-153-125-115.elisa-laajakaista.fi> References: <200812201150.mBKBo55n044624@freefall.freebsd.org> <7d6fde3d0812210133x465c7f47r4722b268029c3905@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7d6fde3d0812210133x465c7f47r4722b268029c3905@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: freebsd-bugs@freebsd.org Subject: Re: bin/95979: burncd(8) fails to fixate CDs X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2008 14:20:52 -0000 On 2008-12-21, Garrett Cooper wrote: > Is there an ATA standard value for timing out? What does cdrecord / > growisofs use? I doubt that the time which fixation should take is standardized. A quick look at wodim (cdrecord fork) and growisofs source suggests that they behave like this: wodim Timeout is 420 seconds divided by burning speed if the drive reports correctly it's state. (There's a different sleep time calculation method if the drive doesn't report it correctly.) If the sleep time / timeout is too short it looks like it doesn't necessarily report an error. growisofs Doesn't use timeout for fixation at all but relies on the drive reporting when fixation finishes. It seems to have quirk(s) for some drive(s). -- Jaakko