Re: FIFO
"Zoran Ljubisic" <[email protected]>
| Newsgroups | gmane.comp.archivers.star.user |
|---|---|
| Message-ID | <007301c5c908$e117c580$fd01a8c0@zoran> |
David Brown wrote: > On Tue, Oct 04, 2005 at 05:23:58PM +0200, Joerg Schilling wrote: > > Linux supports both types of block sizes. 'mt status' should tell > you what the 'tape blocksize' is set to. drive type = Generic SCSI-2 tape drive status = 1191182336 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 0 bytes. Density code 0x47 (unknown). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN > If it is set to a fixed > number (usually 512), then everything is written in blocks of that > size, and the block size on output is arbitrary. Looks like it is not fixed. > If the blocksize is zero, then the tape driver uses the blocks that > are written. I commit: dd if=/dev/st0 of=testblocksize.dd bs=10M count=1 ls -l testblocksize.dd size is 8388608 bytes. Looks like bs=8m works as expected. > mt setblk 0 > > will give you the conventional blocks size. I commit mt setblk 0 just before executing star -c. If I understand you right, I should avoid setblk in my case. Zoran