From owner-freebsd-gnome@FreeBSD.ORG Thu Mar 4 17:14:24 2010 Return-Path: Delivered-To: gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7998106564A; Thu, 4 Mar 2010 17:14:24 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CFED78FC0C; Thu, 4 Mar 2010 17:14:23 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA04599; Thu, 04 Mar 2010 19:14:21 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B8FEA6D.4050607@icyb.net.ua> Date: Thu, 04 Mar 2010 19:14:21 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20100211) MIME-Version: 1.0 To: gnome@FreeBSD.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Joe Marcus Clarke Subject: hald vs dvd+rw X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 17:14:24 -0000 It seems that hald behavior might be causing some issues with re-writing DVD±RW media. I specifically mean the case when media already contains CD9660 or UDF filesystem and is being re-written with new data. It seems that when hald notices old volume going away, it attempts to re-taste the media while a burning program, e.g. growisofs, may be writing data to the media. At the very least it produces messages in system log like the following: kernel: (cd0:ahcich5:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0 kernel: (cd0:ahcich5:0:0:0): CAM status: SCSI Status Error kernel: (cd0:ahcich5:0:0:0): SCSI status: Check Condition kernel: (cd0:ahcich5:0:0:0): SCSI sense: NOT READY asc:4,8 (Logical unit not ready, long write in progress) At the worst, it causes confusion for the burning program. This happens with recent versions of 9-CURRENT and 8-STABLE, when using atacam and ahci driver for programs like growisofs from dvd+rw-tools and cdrecord from cdrecord-devel. And, of course, for frontends that use those as backends. I am not sure how to resolve this properly. Perhaps, hald could have a special treatment for 'Logical unit not ready, long write in progress' sense from TEST UNIT READY command. -- Andriy Gapon