Bug 131052

Summary: nfs mounted quotas broken on Solaris, panasas, and netapps
Product: [Fedora] Fedora Reporter: Jay Hilliard <jay.hilliard>
Component: quotaAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: jay.hilliard
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:05:19 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:

Description Jay Hilliard 2004-08-26 22:32:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

Description of problem:
quota: Error while getting quota from host:/mount: Invalid argument

autofs is supposed to be able to ignore invalid arguments and still
work, but code in this package is NOT allowing invalid arguments. 
This causes quotas to fail on these particular mounts.

we want to ignore certain autofs options and continue to mount because
we have different automount clients out there (non linux) that need them

Version-Release number of selected component (if applicable):
util-linux-2.12-18

How reproducible:
Always

Steps to Reproduce:
1.Solaris exported filesystem with quotas turned on
2.automount map has "noquota" or other ugly options
3.Try to automount and you get the error
    

Actual Results:  quota: Error while getting quota from
fasrel-n1:/rel/sw for 2146: Invalid argument


Expected Results:  Ignore it and continue to mount anyway

Additional info:

Comment 1 Jay Hilliard 2004-09-10 19:40:11 UTC
this is a duplicate of 123620 which there is a fix for, but it's not
yet in fedora updates

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

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