Re: DDS-3 tapetype ???
--On Thursday, June 16, 2005 23:59:28 -0500 Michael D Schleif [EMAIL
PROTECTED] wrote:
Earlier this year, my HP DAT tape drive had problems, and I replaced it
with a Compaq/Sony SDT-9000. Mostly, I am still using the same DDS-3
tapes that I was using, and retired some and added some. My old records
show that I was getting nearly the full 12GB uncompressed tape length.
Since the tape drive change, I have wondered why I didn't seem to be
getting all the data on some tapes. Clearly, with Amanda, some days it
just doesn't want to send a full 12GB to tape; but, mostly, I have been
seeing 9GB going to tape, and balance sitting in holdingdisk.
Today, I did this:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression
off)
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
real364m39.451s
user0m2.724s
sys 0m28.719s
What is going on here?
How can I get a full 12GB tape length?
What do you think?
Are you positive hardware compression is off? You might want to look into
Gene's frequent postings about disabling compression when tapes have
previously been written compressed.
Are you actually hitting EOT on your backups, or is it just the result
of your tapetype setting the length to 9.5GB? If you're not already
hitting EOT, try changing the length in your tapetype to 12GB and see
if more is written.
Frank
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
--
Frank Smith[EMAIL PROTECTED]
Sr. Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: dumper5 pid 10813 is messed up, ignoring it
Rebecca Pakish Crum wrote: on 16.06.2005, 19:47 you wrote to amanda-users@amanda.org: Here's what I have: A server running amanda-2.4.4p4 running on RHE3 intel, and has been for a couple of years. A client running amanda-2.4.4p1 on Sol9, sparc. Yeah, I thought about that, but if that were the problem, wouldn't it be happening on my other 2.4.4p1 clients? I'm looking for a little bit more information on what the problem could possibly be. What causes the dumper to tank all of a sudden? If there's something else failing on this box, I'd kind of like to know. It seems you get this message when a dumper decides to send garbage to the driver (instead of a limited set of commands), or quits suddenly. The last one is most probable. If it dies, there could be many reasons, some even hardware related, e.g. bad RAM, or software related (e.g. out of open file descripters, out of swap space, etc). The fact that it only happend twice on the same host has maybe more to do with the fact that is was trying to dump a level 0 dump, taking much longer, and having a greater chance of being killed. Notice that it is the dumper on the amandaserver that fouled up, not the client sending the dumps. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: DDS-3 tapetype ???
Michael D Schleif wrote:
Since the tape drive change, I have wondered why I didn't seem to be
getting all the data on some tapes. Clearly, with Amanda, some days it
just doesn't want to send a full 12GB to tape; but, mostly, I have been
seeing 9GB going to tape, and balance sitting in holdingdisk.
Today, I did this:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here. It would
be twice or three times as fast, instead of only 2 seconds difference.
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
These two lines are actually a little strange. I would have expected
that the second pass wrote a little bit less then the first pass (and
the difference is the space taken up by the additional filemarks).
But you seem to write more in the second pass. Even 400 Mbyte.
In previous version of amtapetype, this would be reported as a negative
filemark size of -4603 Mbyte (the granularity of measuring is 32K).
What actually happened is that in the first pass, there was a hard write
error, interpreted as an end-of-tape.
This is a symptom of an almost bad tape or tapedrive or dusty heads.
Some OS's report an excessive soft-error rate in the kernel messages.
Do you find anything like that in /var/log/messages?
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here.
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
real364m39.451s
user0m2.724s
sys 0m28.719s
What is going on here?
How can I get a full 12GB tape length?
What do you think?
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out *
***
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I have run the amtapetype command and used the output and entered
into the amanda.conf as below.
# Produced after running amtapetype command.
define tapetype tape-DDS-4 {
comment Produced by tapetype 20gb(hardware compression off)
length 19510 mbytes
filemark 79 kbytes
speed 1740 kps
}
Note the other tapetype parameters are still there which I what I think
is still causing my dumps to fail as is still complaining about dump
larger than tape, 2862305 KB, but cannot incremental dump new disk.
Have I got to comment out the other tapetyps definitions
Here is my ~amdump.6 file output.
From this blurb - tape length 1976320 mark 111 I note that was in my
previous HP
define tapetype HP-DAT {
comment DAT tape drives
# data provided by Rob Browning [EMAIL PROTECTED]
length 1930 mbytes #I have changed this to 2
filemark 111 kbytes
speed 468 kbytes
dumper: dgram_bind: socket bound to 0.0.0.0.990
dumper: pid 28445 executable dumper1 version 2.4.4p2, using port 990
planner: time 3.216: got result for host server.domain.co.uk disk /: 0
- 5735560K, -1 - -1K, -1 - -1K
planner: time 3.216: getting estimates took 3.212 secs
FAILED QUEUE: empty
DONE QUEUE:
0: server.domain.co.uk /
ANALYZING ESTIMATES...
pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due
for level 0) (new disk, can't switch to degraded
mode)
curr level 0 size 2867780 total size 2868209 total_lev0 2867780
balanced-lev0size 2867780
INITIAL SCHEDULE (size 2868209):
server.domain.co.uk / pri 12951 lev 0 size 2867780
DELAYING DUMPS IF NEEDED, total_size 2868209, tape length 1976320 mark
111
planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape,
2867780 KB, but cannot incremental dump new disk] delay: Total size now
286.
planner: cannot fit anything on tape, bailing out
planner: time 3.217: cannot fit anything on tape, bailing out
planner: time 3.217: pid 28441 finish time Thu Jun 16 13:12:52 2005
driver: adding holding disk 0 dir /dumps/amanda size 20971520
Thus have I got to reset anything as Amanda is still thinking of my
previous tapetype.
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again When I tried to comment this out Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote:
Hi again
When I tried to comment this out
Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype
HP-DAT not defined.
How do it start amanda So is uses another tapetype parameter which I
have added to amanda.conf
How about editing that line and putting tapetype tape-DDS-4
so that amanda now looks at the tapetype you just added (at least that
what I presume you did after reading your other message).
Or do I feel that there is actually a little misunderstanding in
how the amanda.conf file finds the tapetype?
The tapetype line instructs amanda you are using tape of
a kind , from all of the kinds that are defined with
the define tapetype xyz {...} groups.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again
The reason to reset as I only left the correct tapetype that was
produced using amtapetype and thus commented out the remainder and I got
this error below
/etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not
defined
So I assume that it's still assuming the previous tapetype and thus I am
unable to backup.
Cheers
On Fri, 2005-06-17 at 13:49 +0200, Paul Bijnens wrote:
Chuck Amadi Systems Administrator wrote:
Hi again
When I tried to comment this out
Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype
HP-DAT not defined.
How do it start amanda So is uses another tapetype parameter which I
have added to amanda.conf
How about editing that line and putting tapetype tape-DDS-4
so that amanda now looks at the tapetype you just added (at least that
what I presume you did after reading your other message).
Or do I feel that there is actually a little misunderstanding in
how the amanda.conf file finds the tapetype?
The tapetype line instructs amanda you are using tape of
a kind , from all of the kinds that are defined with
the define tapetype xyz {...} groups.
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote: I edit the amanda.conf and added the correct defintions from running amtapetype But when I rerun amdump or amflush it still using the previous incorrect tapetype that has smaller tape size than the real required 20GB tape size. Then post amanda.conf -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
On Fri, Jun 17, 2005 at 12:28:51PM +0100, Chuck Amadi Systems Administrator enlightened us: When I tried to comment this out Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf You've added a define tapetype FOO section. Now you need to go back towards the top of the amanda.conf file and find the tapetype HP-DAT line and change it to tapetype YOURNEWDEFINITION. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgp4cnDXERHZD.pgp Description: PGP signature
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi When I do Got this message when I treid that - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. So how do I tell amanda to let go of this tapetype and use another or let me create a new definition. Cheers On Fri, 2005-06-17 at 08:07 -0400, Matt Hyclak wrote: On Fri, Jun 17, 2005 at 12:28:51PM +0100, Chuck Amadi Systems Administrator enlightened us: When I tried to comment this out Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf You've added a define tapetype FOO section. Now you need to go back towards the top of the amanda.conf file and find the tapetype HP-DAT line and change it to tapetype YOURNEWDEFINITION. Matt -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote: Hi Thanks for looking. # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. ... And on line 79: tapetype HP-DAT # what kind of tape it is (see tapetypes below) That should be: tapetype tape-DDS-4 ... # tapetypes # Define the type of tape you use here, and use it in tapetype # above. Some typical types of tapes are included here. The tapetype # tells amanda how many MB will fit on the tape, how big the filemarks # are, and how fast the tape device is. Read the text above again, until you understand what you did wrong. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I am still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk but it's only less than 3gb. Here's my less /var/mail/root ANALYZING ESTIMATES... pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 2862305 total size 2862734 total_lev0 2862305 balanced-lev0size 2862305 INITIAL SCHEDULE (size 2862734): server.domain.co.uk / pri 12951 lev 0 size 2862305 DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark 111 planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape, 2862305 KB, but cannot incremental dump new disk] delay: Total size now 286. planner: cannot fit anything on tape, bailing out planner: time 3.118: cannot fit anything on tape, bailing out Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hello, Chuck, on 17.06.2005, 15:36 you wrote to amanda-users@amanda.org: Hi I am still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk but it's only less than 3gb. Please stop starting threads over and over for the same simple topic. Paste your amanda.conf in a reply to this mail (no attachment) and let us debug your understanding of tapetype-definitions. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED]
Re: DDS-3 tapetype ???
* Paul Bijnens [EMAIL PROTECTED] [2005:06:17:09:51:48+0200] scribed:
Michael D Schleif wrote:
Since the tape drive change, I have wondered why I didn't seem to be
getting all the data on some tapes. Clearly, with Amanda, some days it
just doesn't want to send a full 12GB to tape; but, mostly, I have been
seeing 9GB going to tape, and balance sitting in holdingdisk.
Today, I did this:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here. It would
be twice or three times as fast, instead of only 2 seconds difference.
Yes, indeed. I also tried this:
# sudo /bin/mt -f /dev/nst0 compression 1
# sudo /bin/mt -f /dev/nst0 defcompression 1
# sudo -u backup amtapetype -c -f /dev/nst0 -o
Writing 1024 Mbyte compresseable data: 384 sec
Writing 1024 Mbyte uncompresseable data: 1318 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 2636 sec = 0 h 43 min
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
These two lines are actually a little strange. I would have expected
that the second pass wrote a little bit less then the first pass (and
the difference is the space taken up by the additional filemarks).
But you seem to write more in the second pass. Even 400 Mbyte.
In previous version of amtapetype, this would be reported as a negative
filemark size of -4603 Mbyte (the granularity of measuring is 32K).
In lieu of else to chase, how can this happen? Is this strangeness a
bad thing? How can I find the root cause?
What actually happened is that in the first pass, there was a hard write
error, interpreted as an end-of-tape.
This is a symptom of an almost bad tape or tapedrive or dusty heads.
Some OS's report an excessive soft-error rate in the kernel messages.
Do you find anything like that in /var/log/messages?
No, there are no errors under /var/log/ for the tape drive. The tape I
am using for this was brand new, unsealed yesterday, solely for this
test. It is a hp dds-3 c5708a.
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here.
Yes, in recent versions of amtapetype, it actually puts it in the
comment, as above.
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
I would be more willing to consider hardware problems on my side, if it
weren't for several extenuating circumstances:
[1] Amanda FAQ-O-Matic shows other people ending with same results; but,
I have not found documented resolution.
[2] All of my tapes in circulation have been reporting short lengths in
the `Tape Size (meg)' report field. Prior to replacing the tape
drive, these same tapes were better filled, according to these
reports.
[3] I clean the tape drive once (1x) per week. I do not notice any
unusual lights/LED's while the tape drive is working.
[4] I have successfully restored from these tapes, and using this same
tape drive, on several occasions.
Just for clarification, the brand on the tape drive is Compaq; but, the
only SDT-9000 I find on Google is the Sony brand; therefore, I assume
that Compaq is private branding the Sony drives.
What else can I do?
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: DDS-3 tapetype ???
--On June 17, 2005 9:51:48 AM +0200 Paul Bijnens [EMAIL PROTECTED] wrote: Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write) wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write) These two lines are actually a little strange. I would have expected that the second pass wrote a little bit less then the first pass (and the difference is the space taken up by the additional filemarks). Actually. on my DAT drives I get the same thing. Reliably. Multiple (new) tapes, multiple drives. I think maybe a bug in the tapetype program of some nature. I've only ever run the tests without compression personally. *shrugs*
Re: DDS-3 tapetype ???
On Fri, Jun 17, 2005 at 10:05:44AM -0600, Michael Loftis wrote: --On June 17, 2005 9:51:48 AM +0200 Paul Bijnens [EMAIL PROTECTED] wrote: Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write) wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write) These two lines are actually a little strange. I would have expected that the second pass wrote a little bit less then the first pass (and the difference is the space taken up by the additional filemarks). Actually. on my DAT drives I get the same thing. Reliably. Multiple (new) tapes, multiple drives. I think maybe a bug in the tapetype program of some nature. I've only ever run the tests without compression personally. Have you tried amtapetype with compression intentionally left on? It might confirm that the current results were obtained with compression off. I'm thinking about a possibility where the drive dip switches are set to not allow switching it off. My HP drive has such a switch. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: DDS-3 tapetype ???
--On June 17, 2005 1:37:42 PM -0400 Jon LaBadie [EMAIL PROTECTED] wrote: Have you tried amtapetype with compression intentionally left on? Not yetI can pull out a tape and start a run, it takes about 4hrs on my tape, will report back either later tonight (if i remember) or tomorrow morning. Though I'm separate from the individual who started this thread the results should be interesting. Actually I'll start a 'batch' run with compression on and off and we can see what we get. It'll take atleast 8 hrs to complete so I probably won't have results until tomorrow. Not intending on being here too late tonight. It might confirm that the current results were obtained with compression off. I'm thinking about a possibility where the drive dip switches are set to not allow switching it off. My HP drive has such a switch. -- Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds. -- Samuel Butler
Re: DDS-3 tapetype ???
Michael Loftis wrote: --On June 17, 2005 9:51:48 AM +0200 Paul Bijnens [EMAIL PROTECTED] wrote: Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write) wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write) These two lines are actually a little strange. I would have expected that the second pass wrote a little bit less then the first pass (and the difference is the space taken up by the additional filemarks). Actually. on my DAT drives I get the same thing. Reliably. Multiple (new) tapes, multiple drives. I think maybe a bug in the tapetype program of some nature. I've only ever run the tests without compression personally. What block sizes are you guys using? I mean on the tapedrive not the amanda block size. I have found that a block size of 0 (variable) works best for me on my DDS3 drive. /Andreas
tapetypes
Perhaps I'm missing something obvious, but what is the fascination with generating tapetypes? I thought all it did was let amanda know much data could be expected to fit on a tape. Whether you run tapetype or just start with the nominal capacity of the tape, you may still want to tweak the numbers since not all tapes are the exact same length and not all DLE and dumplevels compress the same. If you strictly use S/W compression then the actual capacity should be close the the advertised native capacity of the tape, and if using H/W compression it's more of a learned guess based on your experiences with the overall compressibility of your data. Either way, you will probably end up with a number that is different from the one that tapetype generates. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: tapetypes
Hello, Frank, on 17.06.2005, 21:25 you wrote to amanda-users@amanda.org: Perhaps I'm missing something obvious, but what is the fascination with generating tapetypes? I think that most people that are new to AMANDA assume that they somehow HAVE TO generate their own special tapetype to tailor their setup to their own single tapedrive. They often assume to get some specific optimization from doing that. In most of the cases it is sufficient to just use one of the tapetype-definitions in the example amanda.conf or choose one from the FAQ-O-Matic (which isn't very up-to-date, to say the least). Maybe this should become another FAQ-entry: Do I have to run amtapetype? But who reads it anyway ;-) ? --- This whole tapetype-mess bugs me for quite a while now, since I got in touch with XML, I play with the thought of providing a tapetype-DB based on XML-entries. No more FOM-digging, just browse the tapetype-DB at amanda.org. Something like the guys from linuxprinting.org provide for printer-drivers. One of the points on my own private AMANDA-wishlist ;) Greets, Stefan mailto://[EMAIL PROTECTED]
lvm and amanda?
I know this isn't necessarily an amanda question, but I have a user who's setup two RedHat Enterprise 4 machines and used lvm. Unfortunately, the devices: /dev/mapper/VolGroup00-LogVol00 has permissions: drwxr-xr-x 2 root root 100 Jun 6 03:58 /dev/mapper brw-r- 1 root disk 253, 0 Jun 6 03:58 VolGroup00-LogVol00 and so amanda can't read these devices for backup. We tried manually setting the groups to disk but on reboot the permissions get reset. We tried editing /etc/lvm/lvm.conf with a umask of 002 and setting the group disk on the directory on /dev/mapper but that didn't stick on reboot. Any thoughts on a permanent solution on setting permissions on these dynamically generated devices? Any information would be appreciated. Oscar
Re: lvm and amanda?
--On Friday, June 17, 2005 17:04:20 -0500 Oscar Ricardo Silva [EMAIL PROTECTED] wrote: I know this isn't necessarily an amanda question, but I have a user who's setup two RedHat Enterprise 4 machines and used lvm. Unfortunately, the devices: /dev/mapper/VolGroup00-LogVol00 has permissions: drwxr-xr-x 2 root root 100 Jun 6 03:58 /dev/mapper brw-r- 1 root disk 253, 0 Jun 6 03:58 VolGroup00-LogVol00 and so amanda can't read these devices for backup. We tried manually setting the groups to disk but on reboot the permissions get reset. We tried editing /etc/lvm/lvm.conf with a umask of 002 and setting the group disk on the directory on /dev/mapper but that didn't stick on reboot. Any thoughts on a permanent solution on setting permissions on these dynamically generated devices? A workaround would be to use tar for your backups, either permanently or just until you figure out where the ownerships/permissions get set in RedHat's LVM. Frank Any information would be appreciated. Oscar -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: lvm and amanda?
Title: RE: lvm and amanda? I have a similar situation, but instead of changing permissions of special devices (particularly RAID devices), which may be protected by SELinux, I list the directories I want to back up in the disklist. Florian Florian Lengyel, Ph.D. Assistant Director for Research Computing Department of Information Resources Graduate School and University Center, CUNY 365 Fifth Avenue, Room 8311.04 New York, NY 10016-4309 Phone: (212) 817-7374 FAX: (212) 817-1615 Email: [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] To: amanda-users@amanda.org Sent: 6/17/2005 6:04 PM Subject: lvm and amanda? I know this isn't necessarily an amanda question, but I have a user who's setup two RedHat Enterprise 4 machines and used lvm. Unfortunately, the devices: /dev/mapper/VolGroup00-LogVol00 has permissions: drwxr-xr-x 2 root root 100 Jun 6 03:58 /dev/mapper brw-r- 1 root disk 253, 0 Jun 6 03:58 VolGroup00-LogVol00 and so amanda can't read these devices for backup. We tried manually setting the groups to disk but on reboot the permissions get reset. We tried editing /etc/lvm/lvm.conf with a umask of 002 and setting the group disk on the directory on /dev/mapper but that didn't stick on reboot. Any thoughts on a permanent solution on setting permissions on these dynamically generated devices? Any information would be appreciated. Oscar
Re: lvm and amanda?
Hello, Oscar, on 18.06.2005, 00:04 you wrote to amanda-users@amanda.org: Any information would be appreciated. Your posting does not tell me if you use DUMP or GNUTAR. From my setup here, which partly dumps a LVM-partition I would also suggest using GNUTAR and listing the mount-dirs inside disklist as Frank and Florian suggested. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED]
amcheck and fqdn names
Hi, I am running Amanda 2.4.5 on FC3 (server and client). I have a problem with amcheck and FQDN names. I cannot get amcheck to successfuly check my config if I don't explicitely use the FQDN name of the host to "amcheck". I have rebuilded the product with --with-fqdn but no change. I have tried to put the fqdn name in my disklist but no change either. I am down to a basic config (1 server and 1 client running onsame system) to demonstrate the problem. Here is hostname info on my system: [reddog] (amanda) linux hostnamereddog[reddog] (amanda) linux dnsdomainnamegpv.az05.bull.com[reddog] (amanda) linux hostname --fqdnreddog.gpv.az05.bull.com Here is my disklist: [reddog] (amanda) linux cat ~amanda/etc/linux/disklistreddog hda1 comp Here is the problem: [reddog] (amanda) linux amcheck -c linux Amanda Backup Client Hosts CheckWARNING: reddog: selfcheck request timed out. Host down?Client check: 1 host checked in 29.996 seconds, 1 problem found [reddog] (amanda) linux amcheck -c linux reddog Amanda Backup Client Hosts CheckWARNING: reddog: selfcheck request timed out. Host down?Client check: 1 host checked in 29.997 seconds, 1 problem found [reddog] (amanda) linux amcheck -c linux reddog.gpv.az05.bull.com Amanda Backup Client Hosts CheckClient check: 0 hosts checked in 0.001 seconds, 0 problems found I have another config on the same server that backups AIX systems that works fine w/o specifying fqdn names? So I don't know what I have this problem against Linux systems? Can someone help me please? Jerome
Re: amcheck and fqdn names
On Fri, Jun 17, 2005 at 07:39:44PM -0700, Jerome Pioux wrote: Hi, I am running Amanda 2.4.5 on FC3 (server and client). I have a problem with amcheck and FQDN names. I cannot get amcheck to successfuly check my config if I don't explicitely use the FQDN name of the host to amcheck. I have rebuilded the product with --with-fqdn but no change. I have tried to put the fqdn name in my disklist but no change either. I am down to a basic config (1 server and 1 client running on same system) to demonstrate the problem. ... Can someone help me please? Build the attached programs, gethostbyname and gethostbyaddr. They were written by JRJackson to mimic the way amanda resolves names. Not all apps do it the same way. Make sure you get proper resolution with the address, the fqdn, and the shortname. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) GetHost.tar.gz Description: application/tar-gz
