Bug 115606

Summary: nfs warning message while mounting remote filesystem
Product: [Fedora] Fedora Reporter: Bernd Bartmann <bernd.bartmann>
Component: util-linuxAssignee: Elliot Lee <sopwith>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: icon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:01:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 114963    

Description Bernd Bartmann 2004-02-13 19:30:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
When mounting a remote nfs share I get a warning message:

mount picard:/home /home
nfs warning: mount version older than kernel

client side is FC2 Test1, server side is RHES3 fully patched

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. mount a nfs share
2.
3.
    

Additional info:

Comment 1 Konstantin Ryabitsev 2004-02-16 20:44:55 UTC
Confirming on fc2-t1.

Comment 2 Elliot Lee 2004-02-24 14:55:55 UTC

*** This bug has been marked as a duplicate of 116269 ***

Comment 3 Konstantin Ryabitsev 2004-02-24 15:02:56 UTC
Oh come on, don't close it as a duplicate of a private bug! That is
teetering on rude.

Comment 4 Hunter Matthews 2004-02-24 15:13:22 UTC
Yes, but now they don't have to fix it.

Comment 5 Hunter Matthews 2004-02-24 15:25:42 UTC
Yes, and my comment was the most rude of all. 
My apologies to all


I will not post to bugtraq while fighting network problems.



Comment 6 Konstantin Ryabitsev 2004-02-24 15:29:57 UTC
Since I can't edit that bug, I'll keep up in this one: :)

This is definitely something that is going to drive our users bonkers,
and us in turn, because we'll have to asnwer to them "it's okay to see
that warning." Can this behavior be changed, or the warning made less
verbose?

Comment 7 Red Hat Bugzilla 2006-02-21 19:01:13 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.