No, we never really researched it. We are aware of a spinlock NFS bug that exists in RHEL4U3 that is fixed in RHEL4U6. This caused some problems during a benchmark at HP a couple of years ago. I don't know if this is the same or different problem. But, I do know that serving the directories from RHELU6 appears to solve our problem, and since we were planning on upgrading our servers in this office eventually, we'll just move the upgrade plan up. At the present time, we have another few HDs on order that should arrive any minute. -- Jerry Feldman <Jerry.Feldman@xxxxxxxxxxxxxxxx> Algorithmics (US), Inc Suite 2-400 275 Grove St. Newton, MA 02466 617-663-5220 617-663-5391 (fax) > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- > bounces@xxxxxxxxxx] On Behalf Of Chet Nichols III > Sent: Thursday, July 17, 2008 11:52 PM > To: General Red Hat Linux discussion list > Subject: Re: NFS problems between RHEL4 U3 and RHEL4U6 > > You ever figure this one out? > Chet > > On Mon, Jul 14, 2008 at 11:57 AM, <jerry.feldman@xxxxxxxxxxxxxxxx> wrote: > > > RHEL4U3 is running a 2.6.9-34 kernel with nfs utils 1.0.6-65. > > RHEL4U6 is running 2.6.9-64 kernel with 1.0.6-84. > > > > I am also aware that there was a spinlock issue in the Update 3 kernel > > that affected us on a several hundred system benchmark a couple of years > > ago, with a patch that was supposed to be in Update 6. I don't think the > > spinlock bug is the issue, but it does look like some type of locking > > issue. The reason I don't think we are running into the spinlock issue > > is that we are not driving the systems heavily. > > > > -- > > Jerry Feldman <Jerry.Feldman@xxxxxxxxxxxxxxxx> > > Algorithmics (US), Inc > > Suite 2-400 > > 275 Grove St. > > Newton, MA 02466 > > 617-663-5220 > > 617-663-5391 (fax) > > > > > > > -----Original Message----- > > > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- > > > bounces@xxxxxxxxxx] On Behalf Of chaim.rieger@xxxxxxxxx > > > Sent: Monday, July 14, 2008 11:47 AM > > > To: General Red Hat Linux discussion list > > > Subject: Re: NFS problems between RHEL4 U3 and RHEL4U6 > > > > > > What version of nfs are they running ? > > > Sent via BlackBerry from T-Mobile > > > > > > -----Original Message----- > > > From: <jerry.feldman@xxxxxxxxxxxxxxxx> > > > > > > Date: Mon, 14 Jul 2008 09:57:29 > > > To: <redhat-list@xxxxxxxxxx> > > > Subject: NFS problems between RHEL4 U3 and RHEL4U6 > > > > > > > > > My primary NFS server is running RHEL4 Update3 (unpatched). I just > > added > > > a few servers running U6. (The specific release I run is specified by > > > our IT department). The problem I am seeing is: > > > When I save an 8MB file from our application on a client RHEL4U3 > > machine > > > the save time is about 1 second. When I perform the same test on a > > > client running RHEL4U6, the save takes about 2 minutes. > > > > > > As a test, I exported a directory from one of the RHELU6 systems, and > > > the save times were good on both an update 3 and update 6 client. So, > > > one solution is to upgrade U3 to U6. (I would probably do a fresh > > > install). But, that requires some downtime, and the server room is not > > > accessible after hours. (All disks are removable so I probably could > > > move the volume group to one of the existing servers to minimize > > > downtime). > > > > > > I would like to know if there is some existing NFS issue between U3 > > and > > > U6. If I could provide a temporary fix, that would be a better interim > > > solution until the additional drives I ordered arrive. > > > > > > -- > > > Jerry Feldman <Jerry.Feldman@xxxxxxxxxxxxxxxx> > > > Algorithmics (US), Inc > > > Suite 2-400 > > > 275 Grove St. > > > Newton, MA 02466 > > > 617-663-5220 > > > 617-663-5391 (fax) > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > -- > > > This email and any files transmitted with it are confidential and > > > proprietary to Algorithmics Incorporated and its affiliates > > > ("Algorithmics"). If received in error, use is prohibited. Please > > destroy, > > > and notify sender. Sender does not waive confidentiality or privilege. > > > Internet communications cannot be guaranteed to be timely, secure, > > error > > > or virus-free. Algorithmics does not accept liability for any errors > > or > > > omissions. Any commitment intended to bind Algorithmics must be > > reduced to > > > writing and signed by an authorized signatory. > > > > > ------------------------------------------------------------------------ > > -- > > > > > > > > > -- > > > redhat-list mailing list > > > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > > -- > > > redhat-list mailing list > > > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > > ------------------------------------------------------------------------ > -- > > This email and any files transmitted with it are confidential and > > proprietary to Algorithmics Incorporated and its affiliates > > ("Algorithmics"). If received in error, use is prohibited. Please > destroy, > > and notify sender. Sender does not waive confidentiality or privilege. > > Internet communications cannot be guaranteed to be timely, secure, error > or > > virus-free. Algorithmics does not accept liability for any errors or > > omissions. Any commitment intended to bind Algorithmics must be reduced > to > > writing and signed by an authorized signatory. > > ------------------------------------------------------------------------ > -- > > > > > > -- > > redhat-list mailing list > > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > > -- > ---------------------------------------- > chet nichols III > chet.nichols@xxxxxxxxx > aim: chet / twitter: chet > http://chetnichols.org > ---------------------------------------- > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list -------------------------------------------------------------------------- This email and any files transmitted with it are confidential and proprietary to Algorithmics Incorporated and its affiliates ("Algorithmics"). If received in error, use is prohibited. Please destroy, and notify sender. Sender does not waive confidentiality or privilege. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. Algorithmics does not accept liability for any errors or omissions. Any commitment intended to bind Algorithmics must be reduced to writing and signed by an authorized signatory. -------------------------------------------------------------------------- -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
