Re: DD and Memory

2003-02-26 Thread Stew Benedict

On Wed, 26 Feb 2003, Charles Carroll wrote:

>   All,
> 
>   Interesting development, was able to dump 3.2Gb of raw data from SCSI 
> tape drive. Used the follow commands:
> 
> mt -f /dev/st0 setblk 0  (this sets the blocksize of the tape drive to 
> variable on SCSI Tape drive Zero)
> 
> dd if=/dev/st0 of=(filename) bs=64k   (This reads the tape, and 
> buffers/writes it in 64k blocks.)
> 

Great - glad you solved the issue.  Sorry I wasn't much help, but at least
it will be archived in the list for the next person.

Stew Benedict

-- 
MandrakeSoft




DD and Memory

2003-02-26 Thread Charles Carroll
	All,

	Interesting development, was able to dump 3.2Gb of raw data from SCSI 
tape drive. Used the follow commands:

mt -f /dev/st0 setblk 0  (this sets the blocksize of the tape drive to 
variable on SCSI Tape drive Zero)

dd if=/dev/st0 of=(filename) bs=64k   (This reads the tape, and 
buffers/writes it in 64k blocks.)

	You can read the whole data stream on a clean tape by not including a 
count of the blocks desired. If you add count=xxx to the dd command you 
will dump to file that many 64k blocks.  Turns out the key to the whole 
thing is the mis-match in block sizes.  The drive needs to be set to a 
variable block size on startup in Mandrake. This is where the "mt" 
command comes into play. Once that is done, dd needs to know how much 
data to transfer each read sequence. We write data to the tape drive in 
the VME unit in 64k blocks, so it needs to read in that size. The 
confusion for me came in that the you can't just use 64k blocks.  In 
case you are wondering, the drive being used is a Exebyte 89001 0-025 
drive. I am hoping that with the cost of solid state drives, and 
reliability of hard drives we can replace them in these units like we 
have in others.
Just waiting on the capacity to get up there. We have a PCMCIA solution 
that handles 10Gb of data, but the Exebyte stores 40Gb.

	Sorry to have troubled you all on this.

	BTW, 9.1 has handled this wonderfully on my 1Ghz Powerbook, with the 
Radeon Mobility Video. Thanks Guys!!

	Charlie Carroll 




DD and Memory

2003-02-25 Thread Charles Carroll
	All,

	I have managed to sort out some of the problems with dd and a raw dump 
to tape drives, only to come up with another one.

	I now get a memory allocation error when I try to run dd.  In order to 
get the tape device to work I loaded the mt package, this allows me
to set the block size of the device to 0. What this actually does is 
make the block size for the tape drive variable. (no fixed size). When 
I try to do dd now instead of an input/output error I now see the tape 
drive spin up, and read access occur, but the program errors out with 
the memory allocation error.  I have checked the drive using the scsi 
generic device driver and all the commands are going correctly. This 
does work on an intel machine under Mandrake 9.

	Suggestions? Comments?

	Charlie Carroll