errors using tar command

[Jeff Hagstrom]

tar: couldn't get uname for uid 60001
tar: couldn't get gname for gid 65534
a /home/m-and-i/O4MI1110.txt 136 blocks

[Geoff Wild]

Just means that the file O4MI1110.txt used to be owned by uid 60001 in group 65534.

User was probably deleted.

You could chown it to a new user (like root for example):

chown root:sys /home/m-and-i/O4MI1110.txt

Rgds...Geoff

[Rick Garland]

Typically the user acct that owned these files was deleted.

[Mark Greene_1]

You can also get this is you untar a file that was created on a different system, and the user and group IDs on both systems aren't the same. It's not fatal to the untar, as the files will just have the numbers and not names associated with them, which you can see with an ls.

mark

[James R. Ferguson]

Hi Jeff:

As already noted, you simply don't have a matching uid/gid in the passwd database for the file(s) in question.

Should you ever want to track done files like this, use 'find' thusly:

# cd
# find . -xdev -nouser | xargs ls -l
# find . -xdev -nogroup | xargs ls -l

Regards!

...JRF...

[Jeff Hagstrom]

I should have noted that I have pages of them. They seem to be located on NFS mounted systems.

[Geoff Wild]

Ah - if on NFS - could mean that the NFS server has different users then your server -(or just different uid's) - main thin is, unless you really need to - don't backup the NFS share - do that on the NFS server instead.


Rgds...Geoff