linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Samuel <samuel@bcgreen.com>
To: Paul Furness <paul.furness@vil.ite.mee.com>
Cc: admin <linux-admin@vger.kernel.org>
Subject: Re: Detailed info about backups
Date: Wed, 27 Oct 2004 05:50:46 -0700	[thread overview]
Message-ID: <417F99A6.2010407@bcgreen.com> (raw)
In-Reply-To: <1098868312.27244.18.camel@zebra.vil.ite.mee.com>

Paul Furness wrote:

> What does "block size" mean on a tape (DLT and LTO). Is it the same as
> old disks, where each file fills up at least one block, even if it's
> much smaller than a block? If I make this smaller, will more small files
> fit on the tape?
Block size refers to how much data is written to the tape in one chunk.
This can have an effect on how much data you can write to the tape..

For each 'block' you write to the tape there is a pre-block gap , block header
and then the actual data (possibly followed by a block trailer with CRC/checksum.

If you write your data in too-small chunks, then you can often end up wasting
more space on the pre-gap and header than you do on the actual data.

If you write your data in too-large chunks, the tape may have to physically
pause and wait for the data transfer to complete before writing  the data
when this happens you 'lose streaming', and the tape has to stop, backup
and get back up to speed to write the next block  This slows down the backup
and adds wear & tear to the drive (and sometimes also wastes more space on
the tape)

> 
> How do I get the tape drive to definitely use it's internal compression
> hardware? I don't think it's working and I need it to be. How can I
> check this from linux? Some of the auto-changers have displays on the
> front that specify whether compression is being used, but others don't.

man st
   for more info on the SCSI tape drivers.


-- 
Stephen Samuel +1(604)876-0426                samuel@bcgreen.com
		   http://www.bcgreen.com/~samuel/
    Powerful committed communication. Transformation touching
      the jewel within each person and bringing it to light.

      reply	other threads:[~2004-10-27 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  9:11 Detailed info about backups Paul Furness
2004-10-27 12:50 ` Stephen Samuel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=417F99A6.2010407@bcgreen.com \
    --to=samuel@bcgreen.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=paul.furness@vil.ite.mee.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).