From owner-freebsd-current Wed Nov 28 6:44:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from noc1.BelWue.DE (noc1.BelWue.DE [129.143.2.1]) by hub.freebsd.org (Postfix) with ESMTP id 228EE37B417 for ; Wed, 28 Nov 2001 06:44:39 -0800 (PST) Received: from obiwankenobi.science-computing.de (blackhole.science-computing.de [193.197.16.3]) by noc1.BelWue.DE with SMTP id PAA04230 for ; Wed, 28 Nov 2001 15:44:37 +0100 (MET) env-from (C.Herrmann@science-computing.de) Received: from scmsrv1.science-computing.de (scmsrv1.science-computing.de [10.148.25.58]) by obiwankenobi.science-computing.de (8.9.3/8.8.8) with ESMTP id PAA20426 for ; Wed, 28 Nov 2001 15:44:37 +0100 Received: from localhost (localhost [127.0.0.1]) by scmsrv1.science-computing.de (8.11.3/8.11.1) with ESMTP id fASEibO60685 for ; Wed, 28 Nov 2001 15:44:37 +0100 (CET) (envelope-from chris@scmsrv1.science-computing.de) Date: Wed, 28 Nov 2001 15:44:37 +0100 (CET) From: Christoph Herrmann To: current@FreeBSD.ORG Subject: cdrecord produces broken CDs on -CURRENT: The Answer ! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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 ? Ciao Christoph &:-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message