From owner-freebsd-current@FreeBSD.ORG Fri Sep 17 04:42:07 2004 Return-Path: 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 71A2416A4CE for ; Fri, 17 Sep 2004 04:42:07 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0924343D58 for ; Fri, 17 Sep 2004 04:42:07 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-64-164-9-59.dsl.snfc21.pacbell.net [64.164.9.59])i8H4g4Nm067140; Fri, 17 Sep 2004 00:42:06 -0400 Message-ID: <414A6B1C.6060706@elischer.org> Date: Thu, 16 Sep 2004 21:42:04 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Jun Kuriyama References: <7macvple1i.wl@black.imgsrc.co.jp> In-Reply-To: <7macvple1i.wl@black.imgsrc.co.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Current Subject: Re: acd0: FAILURE - READ_BIG MEDIUM ERROR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 17 Sep 2004 04:42:07 -0000 Jun Kuriyama wrote: > When I tried to read DVD-R media (written on the same current box by > cdrecord-ProDVD), I got this message at mounting: > > ----- > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x15 ascq=0x00 error=0 > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x15 ascq=0x00 error=0 > cd9660: RockRidge Extension I think this is a scheduler problem of some sort.. > ----- > > Is this harmless or not? I can copy a file from this DVD-R without > problem. > > > And, this DVD-R has a large file (3GB), and ls(1) (maybe stat(2)) > issues an error like this: > > ----- > % ls -l /cdrom/0 > ls: foo.tgz: Value too large to be stored in data type > ----- > > With inserting printf() at kern/vfs_vnops.c:724, I got following > result. Is this related to above READ_BIG error? Or simply something > wrong in other VFS (or CD9660?) layer? > > ----- > line: > printf("kuri: EOVERFLOW: va_size=%llu, OFF_MAX=%llu\n", vap->va_size, OFF_MAX); > output: > kuri: EOVERFLOW: va_size=18446744072600323698, OFF_MAX=9223372036854775807 > ----- > >