Rogier Wolff [EMAIL PROTECTED] wrote:
during boot. I can then reshuffle my disk to have that 50M of data at
the beginning and reading all that into 50M of cache, I can save
Wasn't that one of the goals of the LVM project, along snapshots and
block-level HSM ?
-
To unsubscribe from this list:
Now try this:
cd ~archive
mt -f /dev/tapes/tape0 rewind
tar cvf - . | gzip -9 | dd of=/dev/tapes/tape0 bs=32k
and then:
mt -f /dev/tapes/tape0 rewind
dd if=/dev/tapes/tape0 bs=32k | gzip -d | tar --compare -v -f -
The above is the proper way to talk to a tape drive through
On Sat, 14 Apr 2001, Geert Uytterhoeven wrote:
Do you also mean it is illegal to use blocksize 10 kB (default tar, no gzip)
with a tape drive??
not at all. Infact, with the default settings of the st driver, any
multiple of 512 bytes is ok. The additional dd step is just there to be
sure
In article [EMAIL PROTECTED] you wrote:
So you make gzip use blocks of 32 kB.
no, infact it really makes it using blocks of 4k (a PIPE_SIZE is 4k), so
it is really equivalent to bs=4k. dd doesn't re-join blocks when
they are smaller then bs=, unless you specify obs=32k.
I have been playing
In article [EMAIL PROTECTED] you wrote:
... still, I've investigated on this because amverify gave me a ton of
crc errors... (I REALLY hope that amanda uses proper blocking :)
yes, it does.
This really looks like a st problem, or kernel. Or host adapter, or :)
I have to try 2.4.x soon.
Rogier Wolff <[EMAIL PROTECTED]> wrote:
> during boot. I can then reshuffle my disk to have that 50M of data at
> the beginning and reading all that into 50M of cache, I can save
Wasn't that one of the goals of the LVM project, along snapshots and
block-level HSM ?
-
To unsubscribe from this
Now try this:
cd ~archive
mt -f /dev/tapes/tape0 rewind
tar cvf - . | gzip -9 | dd of=/dev/tapes/tape0 bs=32k
and then:
mt -f /dev/tapes/tape0 rewind
dd if=/dev/tapes/tape0 bs=32k | gzip -d | tar --compare -v -f -
The above is the proper way to talk to a tape drive through
On Sat, 14 Apr 2001, Geert Uytterhoeven wrote:
> Do you also mean it is illegal to use blocksize 10 kB (default tar, no gzip)
> with a tape drive??
not at all. Infact, with the default settings of the st driver, any
multiple of 512 bytes is ok. The additional dd step is just there to be
sure
In article <[EMAIL PROTECTED]> you wrote:
> So you make gzip use blocks of 32 kB.
no, infact it really makes it using blocks of 4k (a PIPE_SIZE is 4k), so
it is really equivalent to bs=4k. dd doesn't re-join blocks when
they are smaller then bs=, unless you specify obs=32k.
I have been playing
In article <[EMAIL PROTECTED]> you wrote:
> ... still, I've investigated on this because amverify gave me a ton of
> crc errors... (I REALLY hope that amanda uses proper blocking :)
yes, it does.
This really looks like a st problem, or kernel. Or host adapter, or :)
I have to try 2.4.x soon.
10 matches
Mail list logo
