On the client, I can see tar able to cope with files with resource forks. If I put the v option during the create, I see it tar up /path/blah and /path/._blah if appropriate. (Sometimes it does it even if the rsrc fork is empty). Also, when I extract the files from the tar archive, things work as they should. The v option shows the resource forks being extracted and ls -l /path/blah/rsrc shows the resource fork in the new file just as before.
But on my server, life is not happy. I can pull over an archive created on the client and the server tar can untar it properly and things appear to be properly connected. But it can not create an archive. I've tried even as root.
I get errors like this:
tar: /tmp/tar.md.vBT4Uc: Cannot stat: No such file or directory tar: /tmp/tar.md.j3l03v: Cannot stat: No such file or directory tar: /tmp/tar.md.CNxS1Q: Cannot stat: No such file or directory tar: Error exit delayed from previous errors
The checksum on /usr/bin/tar is the same so it must be in some support library somewhere.
I've done a disk repair and repair permissions fairly recently.
Any ideas of how to fix this?