From owner-freebsd-bugs Sun Apr 18 0:17:45 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 8E74414CE2 for ; Sun, 18 Apr 1999 00:17:30 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id IAA09422; Sun, 18 Apr 1999 08:15:05 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA96630; Sun, 18 Apr 1999 07:49:18 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904180649.HAA96630@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Timothy J. Lee" Cc: brian@Awfulhak.org, freebsd-bugs@freebsd.org Subject: Re: kern/10519 In-reply-to: Your message of "Fri, 16 Apr 1999 19:28:15 PDT." <199904170228.TAA01410@netcom2.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Apr 1999 07:49:18 +0100 From: Brian Somers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> >Synopsis: Pine 4.10 build gives spurious "No space left on [NFS] device" > >> > > >> >State-Changed-From-To: open->feedback > >> >State-Changed-By: brian > >> >State-Changed-When: Thu Apr 1 00:12:35 PST 1999 > >> >State-Changed-Why: > >> >Is it possible to recheck this on -stable or -current ? > >> >The problem's gone for me after upgrading the server to --stable (Mar 25) > >> > >> NFS server in this bug is a SPARC computer running Solaris 2.5.1, > >> not FreeBSD. Client is FreeBSD 3.1-RELEASE. I'm not exactly sure > >> what you are asking, whether you want to know if the problem occurs > >> with (a) FreeBSD 3.1-STABLE server, or (b) FreeBSD 3.1-STABLE client. > >> > >> Timothy J. Lee (timlee@netcom.com) > > > >Well, I actually upgraded both machines. The server went from 3.1 to > >-stable and the client went to a new cvsup of -current. > > > >I noticed that the problem had gone away when both were on March 25. > > > >Given that your Solaris box is the same, how about upgrading your > >client ? I suspect the answer to that will be ``not that simple'', > >so when you're in a position to upgrade, bear this PR in mind ;-) > > I just installed a new FreeBSD 3.1-19990416-STABLE computer. > This one does have different hardware (SCSI disks vs. EIDE disk > is the main difference, though the motherboard is also different). > > The problem no longer occurs. The Solaris 2.5.1 NFS server (with > kernel patch 103640-24) is the same as it was before with the > FreeBSD 3.1-RELEASE computer showing the bug. Should we close the PR then ? > Timothy J. Lee (timlee@netcom.com) Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message