From owner-freebsd-current@FreeBSD.ORG Sun Apr 23 05:37:18 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08DE616A401 for ; Sun, 23 Apr 2006 05:37:18 +0000 (UTC) (envelope-from harikurniawan@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F1E43D46 for ; Sun, 23 Apr 2006 05:37:16 +0000 (GMT) (envelope-from harikurniawan@gmail.com) Received: by nz-out-0102.google.com with SMTP id o1so609931nzf for ; Sat, 22 Apr 2006 22:37:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=a9vfgBCHDDWvH/g81zhNQoAvZ0nlQN3aKl5aIae4/rj8ryOLxxEuaSu/YVDGj+d1oe4ACZ+Dz50eHyeuw32uXJMkwGWulcNtOEwVoVLv0zX8nQKOf36IBCH1hq4VTA5+yPi24WFa36jvmhtkL2J7EUAN4X5z751Vje2ZOhulZXk= Received: by 10.65.192.12 with SMTP id u12mr2113073qbp; Sat, 22 Apr 2006 22:37:16 -0700 (PDT) Received: by 10.64.201.9 with HTTP; Sat, 22 Apr 2006 22:37:16 -0700 (PDT) Message-ID: <4c40c4e70604222237w1f6778b2j4a2fc0ff1f7df730@mail.gmail.com> Date: Sun, 23 Apr 2006 12:37:16 +0700 From: "Angka H. K." To: current@freebsd.org, sos@freebsd.org In-Reply-To: <20060421180626.GA28049@roadrunner.buck.local> MIME-Version: 1.0 References: <20060421180626.GA28049@roadrunner.buck.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: acd(4) and maximum read block size X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2006 05:37:18 -0000 I have concern about it but my case is different. I have a disk that burn using 6.1-current and it burn good no error with 6.= 1. But when I read it on 7.0 it produce error ("i am not quite remember but something with big..., like reading error sector"). The disk still readable but the access is slow. On 4/22/06, Ulrich Spoerlein wrote: > > S=F8ren, group, > > I'm working on some improvements for recoverdisk[1] to handle optical > media > better. I found it an invaluable tool for recovering old CD-Rs. It also > helps with newer DVDs, when your drive sucks wrt. error recovery. > > recoverdisk tries to read in 1MB, 64kB and SECTORSIZE chunks. This has > the obvious drawback, that it can't really handle audio CDs or mode 2 > CDs with a sectorsize of 2352. > > While this is easily fixed, the acd(4) driver seems to allow no reads > greater than 128kB *for audio CDs*. While this is also not terrible, it > results in roughly 700 error messages per CD, as all the 1MB (1046640 > bytes, more precisely) chunks will fail. > > A side note: Accessing audio CDs via atapicam and dd(1) is completely > impossible. Is the SCSI subsystem limited to multiple-of-512-blocksizes? > > [1] /usr/src/tools/tools/recoverdisk > > Ulrich Spoerlein > -- > PGP Key ID: 20FEE9DD Encrypted mail welcome! > Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD > Which is worse: ignorance or apathy? > Don't know. Don't care. > > >