Bug 140741 - rpc.rquotad failed
Summary: rpc.rquotad failed
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: i586 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Jan Kara
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-22 13:09 UTC by Martin Walter
Modified: 2006-04-26 16:03 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Walter 2005-12-22 13:09:41 UTC 
rpc.rquotad on suse10.0 (quota-3.13-2) fails.
If replaced with rpc.rquotad from suse9.3 (quota-3.11-26) all is OK.

Example:

I have exported /u/6 on a suse10.0 pc. Then in first xterm:

  # mount 127.0.0.1:/u/6 /6
  # /usr/sbin/rpc.rquotad -F

now in another xterm:

 # quota -v np6
 Disk quotas for user np6 (uid 29583): 
 Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
 /dev/sda4    2780  524288  655360             158   51200   64000        

in the first xterm I get:

 rpc.rquotad: Can't stat() given mountpoint /u/6//u/6: No such file or directory
 Skipping...

same but with /usr/sbin/rpc.rquotad vom suse9.3 I get as expected:

 Disk quotas for user np6 (uid 29583): 
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
      /dev/sda4    2780  524288  655360             158   51200   64000        
 127.0.0.1:/u/6    2780  524288  655360             158   51200   64000  

So it seems to me that /usr/sbin/rpc.rquotad has a problem.
Comment 1 Jan Kara 2006-01-24 13:06:03 UTC 
I guess you use NFSv3, right? Can you please post here contents of your /var/lib/nfs/etab after mounting the NFS filesystem?
Comment 2 Jan Kara 2006-04-18 14:08:11 UTC 
Any news here?
Comment 3 Jan Kara 2006-04-21 13:15:14 UTC 
Hmm, I'm closing this bug as INVALID for now as it is in NEEDINFO for too long. If you can still reproduce the problem and can provide the required information, please reopen the bug.
Comment 4 Martin Walter 2006-04-26 16:03:43 UTC 
Sorry, I forgot this bug because I had a simple workaround: ln -s .. /u/6/u
When 10.1 is out I will test it again.
Thanx