Bug 69162 - I don't think bug #64921 is really closed.
I don't think bug #64921 is really closed.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ben LaHaise
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-07-18 11:40 EDT by russr
Modified: 2007-04-18 12:44 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-07-18 15:18:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description russr 2002-07-18 11:40:49 EDT
Description of Problem:
I am concerned that bug #64921, which is marked as CLOSED, is really not
resolved.  It was closed on 2002-05-28, but looking at the six posts that
follow its closure, I am extremely wary of using nsf with any of the various
work-arounds that are mentioned in a production environment.

Bottom Line: I can't risk nsf mounting with RedHat 7.3, and therefore have
stopped using it at work.  If I were to mount, and hang our N.A. servers,
I would be lucky if the IT folks would continue to let me run RedHat at
work.
Comment 1 Ben LaHaise 2002-07-18 13:18:30 EDT
Performance is fine if your nfs mount specifies async.  If that is not the case
for you, please post details.
Comment 2 russr 2002-07-18 13:53:49 EDT
I haven't seen an explicit resolution for this.  From your comment I'm guessing
that if I am using kernel 2.4.18-5, and if I mount using the async option,
that everything will work.  I am also assuming that I do not need to set
nfsvers=2 and I do not need to set rsize and wsize to 8192.

Please confirm what the complete resolution for this bug is (so I don't get
my RedHat boxes disconnected from my company's LAN).  I will then test it
out and report if there are problems.

I just found bug #67199 which appears to be the same thing, but is owned by
arjanv.  It sounds like with 2.4.18-4 this would hang servers, but with 
2.4.18-5 it just performs very slowly.  Can you please confirm?
Comment 3 Ben LaHaise 2002-07-18 13:58:43 EDT
Again, slowly is sync vs async.  This will probably get changed in nfs-utils.
Comment 4 russr 2002-07-18 15:18:02 EDT
I'm sorry, but I'm going to have to ask the question again.  From above:

 From your comment I'm guessing that if I am using kernel 2.4.18-5, and if
 I mount using the async option, that everything will work.  I am also
 assuming that I do not need to set nfsvers=2 and I do not need to set rsize
 and wsize to 8192.

 Please confirm what the complete resolution for this bug is.
Comment 5 russr 2002-07-19 13:19:41 EDT
> On Fri, Jul 19, 2002 at 10:48:16AM -0600, Russ Radke wrote:
> > Using the 2.4.18-5 kernel, turn async on, and don't worry about nfsvers,
> > rsize, and wsize.
> > 
> > Is that it?
> 
> That's it.  Also, the people I've been in conact with at netapp claim the 
> hang is fixed in newer firmware vresions.
> 
>             -ben

Note You need to log in before you can comment on or make changes to this bug.