Can't chgrp. Error - chgrp: changing group of `<file>': Invalid argument Post: 302793895

Sponsored Content

Operating Systems Linux Red Hat Can't chgrp. Error - chgrp: changing group of `<file>': Invalid argument Post 302793895 by venmx on Sunday 14th of April 2013 11:07:41 AM

04-14-2013

Registered User

Can't chgrp. Error - chgrp: changing group of `<file>': Invalid argument

I found that I cannot chgrp for some reason with error:

chgrp: changing group of `<file>': Invalid argument

This happens on all NFS mounted disks on client machines.

We use AD (not my call) for authentication and it also provides groups.

We have a NFS server running Scientific Linux 6.3 which mounts SAN devices on FC connect. These are then exported via NFS. Clients are all CentOS 6.4.

The clients hard mounts the user's home disk with intr,sync and various tuning options. The other disks use autofs.

AD is configured so that each user has a matching UID and GID, essentially making them the exclusive member of their own group. Not useful for sharing files unless you don't mind making all your files accessibly by world, o+.

We need groups so that we can add members who are then able to chgrp what ever files they'd like to share with members of the same group. All seems pretty straight forward so far.

I used to run OpenLDAP with Kerberos to do all this, I had LDAP manage autofs and groups. Everything worked perfectly.

But now I cannot chgrp.

The permissions of the exported directories on the NFS server are:
drwx--x--x root root /san/home
drwxrwxrwx root root /san/otherdisks

But under home each user directory is owned by the user:
drwx--x--x user1 user1 /san/home/user1

NOTE: "other" means machines within same organization using same AD but built by other departments, "this" means the machines I built.

In the following scenarios it fails:

1. As AD user on "this" client machine on own home on "this" NFS server.
2. As AD user on "this" client machine on automounted disk on "this" NFS server.
3. As root on "this" client machine on automounted disk on "this" NFS server.

In the following scenarios it works:

1. As AD user on "this" client on local partitions where permissions allow.
2. As AD user logged in directly on "this" NFS server on any partition where permissions allow, including on SAN disks.
3. As root on "this" file server on any partition.
4. As AD user on "other" clients on export from "this" NFS server.
5. As AD user on "other" clients on export from "other" NFS server.
6. As AD user on "this" client on export from "other" NFS server.

This issue shows itself when I extract TAR files whilst on client machines to NFS exported shares as AD user or root, can't chgrp!

I can do everything else, I can create, delete, even do newgrp and change my default group then create new files belonging to me with GID of new group. But still can't chgrp to any other group I am a member of when on "this" client and "this" NFS server's export.

To me problem looks like it's on the client side, but I cannot find the issue. Checked all directory permissions of shares on server, tried mounting on other clients, tried other client/server on same AD.

I hope I'm concise and simple enough to go by. Please help! =)

venmx

View Public Profile for venmx

Find all posts by venmx

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

stty: : Invalid argument

Hello Everyone; I have a script that is throwing the following message: stty: : Invalid argument The line that gives the message is the following, sailormoon$ scp home/voice.xml newwave@silvermoon:/newwave/config/radius stty: : Invalid argument voice.xml | ...

2. Programming

error "Invalid argument" returned after call sched_setscheduler

the code is below and the was run on Solaris 9. ----------------------------- struct sched_param param; param.sched_priority = 99; if(sched_setscheduler(0, SCHED_RR, &param) == -1) { perror("setting priority"); exit(1); } ------------------------------- after the...

3. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ...

4. UNIX for Dummies Questions & Answers

msgrcv : Invalid argument

Hi All, Please guide me how to get rid : msgrcv : Invalid argument. I am using message queues: msgsnd and msgrcv, I am able to send through msgsnd and receive through msgrcv, but at times i get the belo error. msgrcv : Invalid argument.

5. UNIX for Dummies Questions & Answers

Chgrp and Chown ???

Hi Can anybody please let me know the usage of Chgrp command with an example??? Thanks

6. OS X (Apple)

AFP mount + Chown/Chgrp respecting

Hello all... Does anyone know how to make an AFP mount of home directories (/Volumes/users off of another server) so that any users doing an ssh login retain write permission to their individual folders, read-write permissions to folders chowned to appropriate group... and so that newly created...

7. Shell Programming and Scripting

Can't chgrp, chown on Linux

I have a problem on Linux wherein it doesn't allow me to use the chown and chgrp even if I am the owner of the file. Is this one of the Linux limitations? BTW, I can use chmod.

8. Shell Programming and Scripting

Perl "Invalid argument error"

Hi , we have a issue in server, we are running a perl script to connect our clients, but we are not able to connect, every time we are getting the "Invalid argument error" Even i checked all the necessary perl modules are i installed in this server, #create the listen socket my...

9. Solaris

Chgrp failed on NAS mounted

Hi, I am facing chgrp issue for a directory on a NAS mounted partation. issue details : user1 belongs to two groups grp1(primary) and grp2(secondary) not able to change directory group to secondary. WORKING on /tmp #mkdir /tmp/a #ls -ld /tmp/a drwxr-xr-x 2 user1 grp1 117 Mar 24...

10. UNIX for Beginners Questions & Answers

Mount error in Linux: invalid argument

hi i have an android phone which i think is bricked, so wanted to see what the actual issue is, I flashed it with TWRP recovery image and launched terminal i, was able understand that mount is not happening, it says invalid argument and no such file or directory. Below is what i get while...

LEARN ABOUT NETBSD

chgrp

CHGRP(1)						    BSD General Commands Manual 						  CHGRP(1)

NAME

     chgrp -- change group

SYNOPSIS

     chgrp [-R [-H | -L | -P]] [-fhv] group file ...

DESCRIPTION

     The chgrp utility sets the group ID of the file named by each file operand to the group ID specified by the group operand.

     Options:

     -H      If the -R option is specified, symbolic links on the command line are followed.  (Symbolic links encountered in the tree traversal
	     are not followed.)

     -L      If the -R option is specified, all symbolic links are followed.

     -P      If the -R option is specified, no symbolic links are followed.

     -R      Change the group ID for the file hierarchies rooted in the files instead of just the files themselves.

     -f      The force option ignores errors, except for usage errors and doesn't query about strange modes (unless the user does not have proper
	     permissions).

     -h      If file is a symbolic link, the group of the link is changed.

     -v      Cause chgrp to be verbose, showing files as they are processed.

     If -h is not given, unless the -H or -L option is set, chgrp on a symbolic link always succeeds and has no effect.  The -H, -L and -P options
     are ignored unless the -R option is specified.  In addition, these options override each other and the command's actions are determined by
     the last one specified.

     The group operand can be either a group name from the group database, or a numeric group ID.  Since it is valid to have a group name that is
     numeric (and doesn't have the numeric ID that matches its name) the name lookup is always done first.  Preceding the ID with a ``#'' charac-
     ter will force it to be taken as a number.

     The user invoking chgrp must belong to the specified group and be the owner of the file, or be the super-user.

     Unless invoked by the super-user, chgrp clears the set-user-id and set-group-id bits on a file to prevent accidental or mischievous creation
     of set-user-id or set-group-id programs.

     The chgrp utility exits 0 on success, and >0 if an error occurs.

FILES

     /etc/group  Group ID file

SEE ALSO

     chown(2), lchown(2), fts(3), group(5), passwd(5), symlink(7), chown(8)

STANDARDS

     The chgrp utility is expected to be POSIX 1003.2 compatible.

     The -v option and the use of ``#'' to force a numeric group ID are extensions to IEEE Std 1003.2 (``POSIX.2'').

BSD
								September 25, 2003							       BSD

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

stty: : Invalid argument

Discussion started by: tony3101

2. Programming

error "Invalid argument" returned after call sched_setscheduler

Discussion started by: robin.zhu

3. Solaris

Owner of file gets 'not owner' error for chgrp

Discussion started by: brizrobbo

4. UNIX for Dummies Questions & Answers

msgrcv : Invalid argument

Discussion started by: answers