From owner-freebsd-current Thu Jan 25 14:18:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E86F37B402 for ; Thu, 25 Jan 2001 14:18:09 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA23441; Thu, 25 Jan 2001 14:18:02 -0800 Date: Thu, 25 Jan 2001 14:18:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nathan Parrish Cc: Dan Nelson , current@FreeBSD.ORG, current-users@netbsd.org Subject: Re: > 4GB with NFS? In-Reply-To: <20010125211443.22025.qmail@web10405.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > knowing NFS in general far better than *BSD in specific, I would guess the best > thing to do (if you suspect server/client communication anomaly) is to grab a > snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the > failure immediately, so you're not tracing 4GB of writes... mebbe dd's > seek/skip? or just append to the existing 4GB file. > > also, what command are you using on the bsd's to write the 4GB file? I've lmdd or dd... > definitely seen issues with VLF-capable OS's failing to write past 2/4GB due to > VLF-incapable utilities. (on a related note, is there a need for > vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write > calls? An update on this.... If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a problem (as clients). The problem is therefore in some interaction between this server (see http://www.traakan.com- sorta like a NetApp) and *BSD. Hmm!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message