From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B2E491381F3 for ; Sat, 13 Jul 2013 10:18:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE54DE0AEA; Sat, 13 Jul 2013 10:18:41 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by pigeon.gentoo.org (Postfix) with ESMTP id C940FE0AD4 for ; Sat, 13 Jul 2013 10:18:40 +0000 (UTC) Received: from scdbackup.webframe.org ([212.46.126.165]) by mail.gmx.com (mrgmx103) with ESMTP (Nemesis) id 0LtZfc-1Tzd51443w-010vVi for ; Sat, 13 Jul 2013 12:18:40 +0200 Date: Sat, 13 Jul 2013 12:18:21 +0200 From: "Thomas Schmitt" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99% Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <1480356.OfmO5JXGQV@zeus> In-Reply-To: <1480356.OfmO5JXGQV@zeus> Message-Id: <2958062521403394201@scdbackup.webframe.org> X-Provags-ID: V03:K0:It/Fk7D3l4E0SgmQ7z+SBBqmWB9HKeuoS7JzmNqFdu2OYS9+Dwp ifxrozV3PSZx4A7z1hcP+Eqb3e4OuGojTlrhJBr7t4H8HJuAphXzXOCCkJx4HRE+0jZjaRN TJVM4l1KXrV61B6No7vDze4nWU4YCLtT4mCssKzLrhL7OIaAnK9MMro8OKY9u12m03bpBkh jNh6c63Srv1uQswY2rQoQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: c9f9ae40-4c6f-4421-8ea3-262290170d1e X-Archives-Hash: f5074e7a69426a2d7eeb518789365379 Hi, > maybe the problem is when closing the session or writing some kind of lead- > out, or the like. The problem is that the CLOSE TRACK/SESSION command is appropriate for the end of burning BD-R, only if it is unformatted or if it is formatted to SRM without Pseudo Overwrite. As soon as it is formatted to Pseudo Overwrite, the command is inappropriate, which the burner indicates by the ILLEGAL REQUEST error code (which one would see if K3b would not swallow it). The bug of growisofs is that it formats the BD-R to Pseudo Overwrite but omits to memorize this new state. If the BD-R is already formatted to Pseudo Overwrite when growisofs inspects it, then its state gets memorized and the inappropriate SCSI command is not issued. My patch proposal just sets the memorizing Pseudo Overwrite flag after the medium has been formatted. So growisofs treats it the same as if it had already been formatted when growisofs first inspected it. This avoids the error. Have a nice day :) Thomas