RE
Niall
After erasing,
i'll give you all infos about each questions you asked to
me.
What output do you get from: " mt status "?
[EMAIL PROTECTED] local]# mt -f /dev/st0
status
SCSI 2 tape drive:File number=0, block
number=0, partition=0.Tape block size 4096 bytes. Density code 0x47(
TR-5).Soft error count since last status=0General status bits on(
4101):BOT ONLINE IM_REP_EN
Are you using version 1.2.1 of flexbackup?
Yes
OK - take compression and the tape out of your next
test.
Make a directory /tmp/FlexTest,
set these options and run flexbackup
again.
$compress = 'false';
$device = '/tmp/FlexTest/';
Now " flexbackup -test-tape-drive " will say, 'No use
trying tape drive tests on directories!', but it will tell you if the rest of
your syntax is correct.
Say nothing so
syntax ok
If you get no errors, run it again withoutc
ompression but with the tape:
$compress = 'false';
$device = '/dev/nst0';
[EMAIL PROTECTED] flextest]# flexbackup
-test-tape-drive -compress=false
-device=st0
flexbackup version 1.2.1 (http://flexbackup.sourceforge.net)/etc/flexbackup.conf
syntax OK
||
Checking 'buffer' on this machine... Ok| Checking /bin/sh on this machine...
bash2||T
esting will *erase* the tape currently in the drive!| Hit CTRL-C to abort
within 10
seconds...||
If for some reason this program does not exit within a few minutes,| Hit
CTRL-C, and try adjusting $blksize, $pad_blocks, or
$mt_blksize.||
Rewinding erasing tape...| Creating index key
200506071610|At
block 0.
Writing test file #1
Kilobytes Out 160
At block 0.
Writing test file #2Kilobytes Out
10At block 0.Writing test file #3Kilobytes Out 160At block0
.
Rewinding...Skipping index label...At
block 0.
Reading test file #1Kilobytes Out
160At block 0.Reading test file #2Kilobytes Out 160At block0
.Reading test file #3Kilobytes Out 160At block
0.
Comparing...Les fichiers
/etc/flexbackup.conf et /tmp/test2.3734 sont différents.
FAILURE! Problem with tape driver orp
arameters. Please see the FAQor try changing the $blksize,
$pad_blocks, or $mt_blksize settings.
[EMAIL PROTECTED] flextest]# flexbackup
-test-tape-drive -compress=false -device=nst0
flexbackup version
1.2.1/etc/flexbackup.conf syntax OK
Errors:$device must be set to a
directory, a local device, or a remote device
Please answer the list rather than me personally, so
that others may benefit and offer further advice.
Good luck,
Niall
On Mon, 6 Jun 2005 [EMAIL PROTECTED]
wrote:
Hi Niall.
Yes, I've already tried all this
feature.
For the compression to I've already tried bzip,
gzip, hardware and so on.
My impression is the next one.
After each
flexbackup-test-tape-drive
It send me
Comparing...
directory /etc/flexbackup.conf and
/tmp/test2.10734 are différents
FAILURE! Problem with tape driver or parameters.
Please see the FAQ
or try changing the $blksize, $pad_blocks, or
$mt_blksize settings.
SO I've tried to see what is talking about this
/tmp/test.
I modified the script and I copy them into a
directory and when i
open it it was just the
/usr/bin/flexbackup.
SO no idea but I continue.
Thanks a lot for your help
-Message d'origine-
De : Niall Brosnan [mailto:[EMAIL PROTECTED]] Envoyé : lundi 6
juin 2005 11:46 À : CHEVALIER, Erwan -Syntegra
FR Objet : Re:
[flexbackup-help] blksize parameters
(fwd)
Hi Erwan,
here is the message as sent to the list on
Thursday.
Do you usually receive list mail?
Hope it helps,
Niall
-- Forwarded message
--
Date: Thu, 2 Jun 2005 11:29:06 +0100
(IST)
From: Niall Brosnan
[EMAIL PROTECTED]
To:
flexbackup-help@lists.sourceforge.net
Subject: Re: [flexbackup-help] blksizep
arameters
Dear Erwan,
From:
[EMAIL PROTECTED]
Dear Flexbackup users,
I've tried all blksize between 0 and 512
which my max, and none of
this values is correct, so anyone can
explain to me, where i'm wrong.
Here is my Flexbackup.conf
I assume you are using linux, and you should
first change this setting:
$device = '/dev/st0';
to
$device = '/dev/nst0';
This is very important!
Dell Powervault 100T DAT 72 with magnetic
tape of 36-72 GB.
If your tape drive has compression turned on,
you should not use
software compression.
I would recommend using software compression
where possible as you
will get better predictions on size, and you
will get better
portability of your backups.
It's far easier to recompile bzip2 for a new
platform than it is to
reverse engineer a compression algorithm on a
chip when your Dell tape drive dies.
What errors are you seeing in
/var/log/flexbackup ?
Why do you feel that the blks