What you need is a GFS version of rquotad. Don't know if it exists or not, but that's what you need.
-Ross
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Doug Tucker Sent: Tuesday, May 13, 2008 11:25 AM To: CentOS mailing list Subject: Re: [CentOS] GFS + quotas
gfs_quota command does NOT exist on clients that are mounting the cluster via nfs. on a standard nfs export from a linux ext3 file system, when you run the quota command from a client, it makes an rpc call to the nfs server, and the nfs server returns the quota on the mounted file system...with gfs as the underlying file system, it doesn't appear the quota values are passed to the exported nfs
On Mon, 2008-05-12 at 19:15 -0230, Scott Thistle wrote:
Use gfs_quota command.
man gfs_quota
gfs_quota <list|sync|get|limit|warn|check|init> [OPTION]
On Mon, May 12, 2008 at 6:54 PM, Doug Tucker tuckerd@engr.smu.edu wrote: I have 2 machines in a cluster using GFS, that many client mount up via nfs. We use quotas extensively here, is there a way from a client machine to check a users quota? Standard quota command on client machines do not work like they do when checking a
non-gfs nfs
mounted file system. The quotas do work however, when auser exceeds
quota and tries to write a file, it tell them that quota has been exceeded. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.