From owner-freebsd-current Wed Nov 28 9:22:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6B8FB37B405 for ; Wed, 28 Nov 2001 09:22:34 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id fASHLsS23031; Wed, 28 Nov 2001 10:21:54 -0700 (MST) (envelope-from ken) Date: Wed, 28 Nov 2001 10:21:54 -0700 From: "Kenneth D. Merry" To: Christoph Herrmann Cc: current@FreeBSD.ORG Subject: Re: cdrecord produces broken CDs on -CURRENT: The Answer ! Message-ID: <20011128102154.A23009@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from C.Herrmann@science-computing.de on Wed, Nov 28, 2001 at 03:44:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 28, 2001 at 15:44:37 +0100, Christoph Herrmann wrote: > > The Problem was the use of vfs.ioopt=2 ! > As long as vfs.ioopt is 1 or 2 the CDs are broken and with > vfs.ioopt=0 the CDs are o.k. > > I didn't see any other problems with the use of vfs.ioopt=2, > especially no Filesystem corruption :-). Are there other known > problems withs vfs.ioopt != 0 ? I'm sort of surprised you didn't see any filesystem corruption with vfs.ioopt turned on -- physio uses the same mechanism as the pass(4) driver for getting data into and out of the kernel. (vmapbuf()) Matt Dillon said almost a year ago that the vfs.ioopt code was broken, but you'd have to ask him to explain it, I don't remember what the problem was. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message