Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Anybody have any suggestions using dd to extract an image copy off of a DLT VS160 tape? The problem is that a large backup was overwritten with 4 megs of data. By normal means, the previous backup is gone. The tape drive is properly configured in SUSE 9.2 - details below. The 4 meg backup is 4065280 bytes in size. I have to use a block size of 65536 or larger (bs=64k) otherwise get "cannot allocate memory" error. So far I can only get the backup header off the tape. Some examples I've used so far are:
dd if=/dev/st0 of=/media/tape.dd bs=64k
dd if=/dev/st0 of=/media/tape.dd bs=1024k
dd ibs=1024k conv=noerror,block if=/dev/st0 of=/media/tape.dd
dd if=/dev/st0 bs=4065280 skip=1 | dd bs=1024k | dd of=/media/tape.dd seek=1
and various others using different block sizes etc.
Tape drive info:
st: Version 20040403, fixed bufsize 32768, s/g segs 256
(scsi2:A:5): 160.000MB/s transfers (80.000MHz DT, offset 96, 16bit)
Vendor: QUANTUM Model: DLT VS160 Rev: 2500
Type: Sequential-Access ANSI SCSI revision: 02
Attached scsi tape st0 at scsi2, channel 0, id 5, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
Attached scsi generic sg0 at scsi2, channel 0, id 5, lun 0, type 1
mt -f /dev/st0 status
drive type = Generic SCSI-2 tape
drive status = 1342177280
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code 0x50 (unknown).
Soft error count since last status=0
General status bits on (45010000):
BOT WR_PROT ONLINE IM_REP_EN
Thanks, I just did and got the same results. I'm begining to think it's just a limitation of dd; it reaches the eof mark on the first record, which is the job header of the backup tape and quits. That's why I can't get past the first filemark. There's gotta be a way to get that data that's lying beyond the 4 meg worth of overwritten info.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.