Joshua Baker-LePain ([EMAIL PROTECTED]):
> On Tue, 9 Oct 2001 at 9:08am, Jeremy Wadsack wrote
>> So do you have any idea how tapetype wrote 9.5GB to a 7GB tape?? If
>> hardware compression would have made it less, then do you think
>> that there was some kind of tape error?
> No, I have no idea. But if you can figure it out, patent it quick! ;)
> Actually, the fact that your filemarks are nearly 900MB big would seem to
> indicate that there *is* some sort of a hardware/software/firmware/driver
> issue.
It was working just fine before I changed the tape type. I had been
using these parameters:
length 5000 mbytes
filemark 48 kbytes
speed 1000 kbytes
But I need to use the full length of the tapes.
> What OS are you running?
Linux, 2.2.16 kernel. It's Cobalt OS based on Red Hat.
> Is there some sort of a st.conf file that
> needs updating?
None that I can find.
>> > Do you mean that in a single night's run, using multiple tapes,
>> > you're only getting 2GB per tape?
>>
>> I'm only using one tape per run. But it's only putting 2GB (1GB last
>> night) on the tapes that had 5GB last week. The change that resulted
>> in this was the change of tapetype.
> That may very well have to do with the filemark value, again.
Ok, so what is the filemark and what do I do with it? (This doesn't
mean anything to me: "Basically tapetype writes random data to tape
and sees how much it is able to write. Then it does it again, writing
filemarks along the way. ")
According to the article on backupcentral.com, "The length and
filemark values are used by AMANDA only to plan the backup schedule."
But I guess that would explain why there are no other errors -- the
scheduler already decided to only dump 1 - 2 GB.
So what should I set it to? Or do I need to figure out why it's
failing? The previous definition (from the tapetype list) had 48kb for
the filemark and at least put 5GB on the tape. If I use the old tape
type and 7000mb I still only get about 2GB on it.
> So to write in uncompressed mode, you do 'mt -f /dev/nst0 setdensity
> 0x15',
Do I need to do this every time the server starts? Is this something
stored in mt (like block size), not the drive?
--
Jeremy Wadsack
Wadsack-Allen Digital Group
