Les Mikesell writes: > On Thu, 2006-01-12 at 10:04, Sim wrote: > > > # tar -tz -f /dev/nst0 > > > > # tar -tz -f /dev/nst0 > > tar: /dev/nst0: Cannot read: Cannot allocate memory > > tar: At beginning of tape, quitting now > > tar: Error is not recoverable: exiting now > > > With "bzip2 compression from BackupPC" and "tar tfj /dev/nst0" > > > > # mt -f /dev/nst0 rewind > > # tar tfj /dev/nst0 > > ./backup/ > > ./backup/aaa > > ./backup/bbb > > ./backup/ccc > > tar: Skipping to next header > > > bzip2: Data integrity error when decompressing. > > Input file = (stdin), output file = (stdout) > > > > It is possible that the compressed file(s) have become corrupted. > > You can use the -tvv option to test integrity of such files. > > Most tape drives won't continue past a data error. This > looks like some kind of hardware issue, perhaps with the > block size on the tape. If you have enough space on disk, > can you try reading the tape into a file with dd and then > see what tar says about it?
I've always wondered what happens to the blocking factor when you use -z or -j with tar. Does tar re-block the output from gzip or bzip2? Do you have to specify -B or -b nnn to force correct blocking when using a tape with -z or -j? Craig ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
