topic Re: Cannot change ownership to uid 673, gid 100: Operation not permitted in Operating System - Linux

Cannot change ownership to uid 673, gid 100: Operation not permitted

yogesh kumar_2 — Thu, 13 Nov 2008 14:07:24 GMT

I have written one backup script in linux workstation,(as a user) so the backup script generated one .tgz file.The script moving .tgz to /net/tps-bcd/backup.

#ex:backup.yogesh_rip-2008-11-13-18-05-37.tgz(in /net/tps-bcd/backup)
I use "tar zxf yogesh_rip-2008-11-13-18-05-37.tgz" to extract the .tgz file.It is working fine.

But,The script i copied to the root user and i scheduled the script it was working fine.The backup taken over in /net/tps-bcd/backup.Then i tried to extract the .tgz file.But its showing below error

#tar: ae/yogesh_rip/Graphics/vectorPack.c: Cannot change ownership to uid 673, gid 100: Operation not permitted

Re: Cannot change ownership to uid 673, gid 100: Operation not permitted

skt_skt — Thu, 13 Nov 2008 19:53:42 GMT

is that account still avaialble ? may be deleted after your backup?

Re: Cannot change ownership to uid 673, gid 100: Operation not permitted

yogesh kumar_2 — Fri, 14 Nov 2008 03:44:58 GMT

The user account is there.

see after copying to /net/tps-bcd/backup(as a root user) its showing file owner and group owner for the .tgz file is "nfsnobody".

Re: Cannot change ownership to uid 673, gid 100: Operation not permitted

Markus Schibli — Fri, 14 Nov 2008 08:28:38 GMT

you said you copied the file as root and see now the ownership of the copied file is "nfsnobody". I assume, you copied the file to an NFS share. This is a normal behavior, since per default on a nfs exported fs the root user of the nfs client is mapped to the uid of nfsnobody, which is normaly uid = 65534 .

If you want that the nfs client root user is also root on the NFS share too, you have to export the NFS share on the nfs server with the flag no_root_squash .

regards
markus

Re: Cannot change ownership to uid 673, gid 100: Operation not permitted

Mike Stroyan — Fri, 14 Nov 2008 18:56:21 GMT

The error message is coming from tar because it is unpacking the file as a user that is not root and not "uid 673, gid 100". When the tar file was written it noted the ownership and permissions of all of the files it backed up. When you try to unpack it you will need to do that as root if you want it to match all of the same arbitrary ownership and permissions. (If all the files belong to the same uid that unpacks the file then there is no problem either.)

The ownership of the tar file itself is not an issue here.