NFS problems between RHEL4 U3 and RHEL4U6

[jerry.feldman at algorithmics.com]

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 at algorithmics.com>
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 at redhat.com [mailto:redhat-list-
> bounces at redhat.com] On Behalf Of chaim.rieger at gmail.com
> 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 at algorithmics.com>
> 
> Date: Mon, 14 Jul 2008 09:57:29
> To: <redhat-list at redhat.com>
> 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 at algorithmics.com>
> 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 at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
> 
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?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.
--------------------------------------------------------------------------