NFS tar errors

I am preparing to install PHP-Nuke. I ftp (binary) the tar.gz up as I have done in my other installations. When I untar it, I get strange I/O errors and NFS complaints. The are different each time I run it. If I nice the command, I get fewer errors.

Do you have any ideas? Seems like I'm on a mis-behaved NFS share.

[snip]$ tar -xf PHP-Nuke-6.5.tar.2
tar: html/images/amazon/0072127317.jpg: Cannot close: Input/output error
tar: Error exit delayed from previous errors
[snip]$ tar -xf PHP-Nuke-6.5.tar.2
tar: html/admin/language/lang-slovak.php: Cannot close: Input/output error
tar: html/admin/links/links.reviews.php: Cannot utime: Input/output error
tar: html/admin/links/links.submissions.php: Cannot close: Input/output error
tar: html/images/admin/downloads.gif: Cannot utime: Input/output error
tar: html/images/red_dot.gif: Cannot utime: Input/output error
tar: html/images/blocks/ur-registered.gif: Cannot close: Stale NFS file handle
tar: html/images/blocks/ur-registered.gif: Cannot utime: Stale NFS file handle
tar: html/images/blocks/ur-super.gif: Cannot utime: Input/output error
tar: html/images/arrow.gif: Cannot utime: Input/output error
tar: html/modules/AvantGo/language/lang-hungarian.php: Cannot close: Stale NFS file handle
tar: html/modules/AvantGo/language/lang-hungarian.php: Cannot utime: Stale NFS file handle
tar: html/modules/AvantGo/language/lang-russian.php: Cannot utime: Input/output error
tar: Error exit delayed from previous errors
[snip]$

Since you're using command line anyway, use:
wget url-of-the-php-nuke-site-download , like:

wget http://aleron.dl.sourceforge.net/sourceforge/phpnuke/PHP-Nuke-6.5.tar.gz

Skip the download/upload process, and just bring it directly to the server.

Good luck,

BobS

Thank you for the suggestions, but the problem is not corruption of the gz, or the tar, but an I/O problem upon writing to the disk. (And because I'm good at screwing things up and also skeptical, I went ahead and tried it and I'm able to duplicate the problem.) The problem is when tar attempts to write to disk. Very odd.

I'm also seeing the same problem with just a plain copy (cp).

odd.

Try untarring it in /tmp.