tar: write error: unexpected EOF

[Happy Huang]

I use a DLT80 driver to do the data backup in a Solaris 2.6 server. The backup command I use is: tar cvfp /dev/rmt/0un /vobs . (/vobs is the directory to be backup) But when I check the backup log, I find the error message as the title: tar:write error: unexpected EOF. I've tried to use a new tape, but still got the same result. Such error message occurs not at the end of the backup log file, but somewhere unexpeted. And to my strange, I use the same DLT driver to backup other directory in the same server, no such error message occurs. And the volumn of /vobs direcory is not very huge and should be held in one tape.
So anyone here can give me some advice to solve the problem. Thank you!

[Zeev Schultz]

Hm,probably /vobs is a certain type of filesystem that has a special requirements how
to be treated?

Zeev

[Francisco J. Soler]

What is the storage size?

Perhaps in the /vobs directory has a file greather than 2 Gb or 8 Gb.

Frank.

[Happy Huang]

I've checked the size of the files under /vobs directory, and no lagrge file whose size exceeds 2GB. And all the file under /vobs are normal data files.

[Francisco J. Soler]

Do you have enough space in another patition?
If yes, you could try a tar over the hard disk to see what happens.

tar cvfp /partition_with_space/tarfile.tar /vobs

Frank.

[Bill McNAMARA_1]

if this is clearcase, verify you've got a valid view set. If it's not so big, try to tar it to file for later transfer to tape.
Make sure that your tape device is unique on the bus.

[Zeev Schultz]

Ok,try using fbackup and see if it fails as well.If not - you have some tar problem,could
be patching issue.Else - you've probably files
problem,could be clearcase-something or else.

Zeev

[Zeev Schultz]

sorry,its ufsbackup on Solaris I beleive :)

[Chris Vail]

Check the /etc/fstab to see if the largefiles option is listed. Our entry looks like:
/dev/vgAPPS/lvolAPPS1 /usr/local/apps vxfs rw,largefiles,delaylog 0 2


Chris

[Tom Danzig]

Check to density of the tape you are using. If it's of newer technonlogy than the drive, you can get this message.

I've seen this error when trying to use a DDS2 tape in a DDS1 drive.