Hello list! A big "thanks!" to all XFS developers for a great product. Now, to the point! We're using an XFS file system created on an LVM with a standard kernel (2.6.32-431.3.1). We're using quotas without an issue, with the exception of the group quota. It seems that group quotas are ignored at times, at least from our configuration (we use remote user and group look-ups and authentication). I've only been able to get root running sudo -g dd.. to create a group file which reflects changes in the group quota limit. We've mounted the file system in question with both user and group quotas enabled; I didn't see anywhere in the man page that said this isn't possible, although I did see where group and project quotas cannot be used simultaneously on the same file system. Has anyone experienced this behavior before? I feel that I did some pretty good searching in the archives, Google, and the BugZilla page, but there were no "real" results which seemed to describe the same issue we're facing. Strace didn't provide any clues either. I don't think it's a sync issue because I've allowed a few days to pass in between "test" runs. I've tested the quota by: 1.) Using sudo -u user -g group dd.... on both the exported file system and its mount path on the server itself. 2.) Using sudo -u user -g group dd.. on the client and the file system's mount path. 3.) Using sudo -g group dd... on both the exported file system and its mount path on the server itself; this method produces expected results. 4.) Using sudo -g group dd.. on the client and the file system's mount path; this method also produces expected results. Items #1 and #2 produce the error. I just wanted to ping the list before creating a local testing group to see if it's an issue with remote group look-ups. Thank you, John DeSantis _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
