From owner-freebsd-stable Tue Feb 9 19:55:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02863 for freebsd-stable-outgoing; Tue, 9 Feb 1999 19:55:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02858 for ; Tue, 9 Feb 1999 19:55:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id TAA77997; Tue, 9 Feb 1999 19:55:20 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Feb 1999 19:55:20 -0800 (PST) From: Matthew Dillon Message-Id: <199902100355.TAA77997@apollo.backplane.com> To: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS + cdda2wav References: <19990209233951.A402@broccoli.no-support.loc> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Hello Matthew, : :here's s.t. I can reproduce on all machines: If you try to :read audio data from a CDROM using cdda2wav (latest version; :shipped with cdrecord-1.8a16) and the resulting audio file :is on an NFS, it will be 50k-100k too small. I tried this :with all flavors NFS v2/v3 TCP/UDP--the same. : :cdda2wav writing to a local FS works perfectly. Not that I :need to use it w/ NFS--it's a bad idea anyway--but it may :help to get NFS more stable. : : Bjoern Bjoern, ktrace the program run. I suspect the problem is not NFS but that the write() latency is causing one of cdda2wav's forked processes to exit and kill its child before the child finishes writing. ktrace -t cn -i cdda2wav .... kdump -R | less Try to match up reads from the CD to writes to the output file. See if the final couple of read/write's match up. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message