SUMMARY: Tape Drive errors

joe macdonald <joe_macdonald25-/[email protected]>
Newsgroups gmane.linux.admin.managers
Message-ID <[email protected]>
Hi,

Lots of people emailed me to let me know that I was
missing a "-" in the command line.  well, that was
only a typo in the message, I didn't forget it on the
actual command line. :)  

I ended up going into the SCSI BIOS and disabled
"Initiate Wide Negotiation".  This set the sync
transfer rate to the lowest possible value, 40MB/s.  
The problem seems to have gone away now.

Does this make sense for a tape drive?  Should wide
negotiation be disabled?  I assume the tape drive
isn't capable of more than 40MB/s anyway (DLT-IV
drive).

I backed up about 9GB of data and it took roughly 2
hours over switched 100mbit fdx ethernet, writing to
the remote tape drive.

Joe

Original question below:
> I'm backing up a database server via tar over an
> ethernet to a remote tape.  Both servers are
> connected
> to the same switch, 100mbit fdx.  There is minimal
> traffic except for the actual tar.
> I'm running the command:
> tar -cvpf . | rsh remotebox buffer -o /dev/tape
> 
> Tar version is GNU tar 1.13
> 
> The tar command randomly chokes, usually on large
> files. Here's the output: 
> 
> buffer (writer): write of data failed: Input/output
> error bytes to write=10240, bytes written=-1, total
> written 
>      8070K
> Broken pipe
> 
> Similiar problems occur if I use GNU tar's
> user@host:file option.
> 
> Anyone know what's going on here and a possible fix?
> 
> Much appreciated.

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers-35TzE1X9F6582KRnZfj+bdi2O/[email protected]
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.