Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Output of dmesg:
st0: Sense Key : Aborted Command [current]
st0: Add. Sense: Information unit iuCRC error detected
st0: <<vendor>> ASC=0xff ASCQ=0xffASC=0xff <<vendor>> ASCQ=0xff
Errata on LSI53C1030 occurredsc->req_bufflen=0x2800, xfer_cnt=0x00,difftransfer= 0x1400
st0: Sense Key : Medium Error [current]
These are SCSI codes...
So "Medium Error" would indicate that you should try
1. Using a cleaning tape.
2. (re)-initialize your tape.
3. Try a new tape.
When I said "cleaning tape", I meant a special cleaning tape that runs for a few minutes.
It has a very mild abrasive to clean the tape heads by removing any accumulated "oxide".
You have to buy these tapes and they should be run according to the recommended schedule.
One cleaning tape is good for several dozen cleaning cycles - probably at least a couple of years - depending on tape drive usage.
@JeremyBoden Has this drive ever worked properly?
How does reading a small file from the tape compare with what was written to it?
i did it and getting the correct data if the file size is less.
according to the HP LTO document To enable large transfers to tape under Linux (>64 KB per write),
i have to set the ST_BUFFER_BLOCKS for that i have to edit the file /usr/src/linux/drivers/scsi/st_options.h and change the definition of ST_BUFFER_BLOCKS but the file st_options.h is not present in my centos6.5
is there any other way through which i can set buffer block or it is having different name...???
Is this definitely for your model of tape drive?
SCSI covers a vast range of speeds - the last non-enterprise one I saw was 320 MBytes/sec
A 64KB buffer has to be way to small for a high speed streaming tape.
Since you are supposed to alter a source file, presumably you need to re-compile your tape driver?
I wouldn't have a clue on how to do this.
If it is a block under run (possible with streaming tapes I guess - I've only seen this on CDs personally) then have you tried using the device blocking options? like -b 2048 (1MB).
The problem may have nothing to do with the driver size, but just the amount of data provided by tar at one time.
Another option is to pipe the output of tar to dd and use dd for blocking huge records. (note: using large buffers on both wouldn't hurt, but this is only for testing. I would expect the tar buffer controls to be the better choice).