From owner-freebsd-current Wed Oct 14 19:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15415 for freebsd-current-outgoing; Wed, 14 Oct 1998 19:28:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.NET (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15409 for ; Wed, 14 Oct 1998 19:28:18 -0700 (PDT) (envelope-from green@zone.syracuse.NET) Received: from localhost (green@localhost) by zone.syracuse.NET (8.8.8/8.8.7) with ESMTP id WAA21319; Wed, 14 Oct 1998 22:27:35 -0400 (EDT) Date: Wed, 14 Oct 1998 22:27:35 -0400 (EDT) From: Brian Feldman To: Greg Lehey cc: Julian Elischer , Mike Smith , "Alex G. Bulushev" , Daniel Rock , current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: <19981015115155.O586@freebie.lemis.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 I've done some NFS experimentation on my box, and basically, I try to test a lot of the new technologies (and older) in FreeBSD. Some of the less successful combos I've tried were: mount_union anything NFS mounting and beating on the FS floppies with softupdates 2 vnode pan60's on 2 SoftUpdates partitions, CCD'd, and made ino a new fs, beat on etc. And beating on as defined something like: #!/bin/sh i=0 while [ $i -le 100 ]; do mkdir $i cd $i i=`expr $i + 1` p=0 while [ $p -le 100 ]; do date > a$p p=`expr $p + 1` done done But I fear these are just the wild experiments of a 15-year-old :-) Brian Feldman On Thu, 15 Oct 1998, Greg Lehey wrote: > On Wednesday, 14 October 1998 at 22:16:21 -0400, Brian Feldman wrote: > > On Thu, 15 Oct 1998, Greg Lehey wrote: > > > >> On Wednesday, 14 October 1998 at 10:28:14 -0700, Julian Elischer wrote: > >>> On Wed, 14 Oct 1998, Mike Smith wrote: > >>>>> Perhaps this could be the problem with NFS "hanging" certain people all > >>>>> the time? (not the pine thing) The system spending way too much time > >>>>> inside the kernel transmitting NFS packets.... > >>>> > >>>> No. Lack of ACCESS caching makes us slow and eats the network (because > >>>> we are very good at generating/sending/receiving them). > >>>> > >>>> If there's someone out there that wants to work with the very best NFS > >>>> people in the business to sort out our problems, please let me know. > >>>> NetApp are keen to see our issues resolved (it will mean less angst > >>>> for them in the long run, as they have many FreeBSD-using customers). > >>>> > >>>> Right now, we are accumulating a bad NFS reputation. 8( > >>> > >>> I thought kirk was doing that.... > >> > >> I hope not. > > > > Well, according to Jordan's "non-verification" to my alluding that since > > Dr. McKusick was committing NFS deltas, he was the mysterious contracted > > NFS fixer-upper. > > Yes, I think you're probably right, though I don't know why nobody has > confirmed or denied it. My comment related to Julian's undirected > comment, and wasn't intended seriously. > > > Last time I checked, he didn't really do his entire job if that was > > to totally fix NFS.... but hey, I don't use NFS much if ever, so I > > won't Complain... > > I use NFS. I'd really like to see it fixed. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message