Re: hdd makes problems -- dma
Sebastian Ksters wrote:
Hi together,
i tried to setup a new amanda server but the hdd makes problems. It's not possible for me to activate the DMA-Mode.
Hdparm d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma= 0 (off)
dmesg | grep had
hda: ST340015A, ATA DISK drive
hda: host protected area = 1
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63
hda: hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } ??
hda: drive_cmd: error=0x04 { DriveStatusError } ??
Hi,
Prolly a problem with the driver for the IDE controller.
'lspci' will show which IDE controller you have. Look for this type in
the kernel-config (make menuconfig) or load the right module
(/etc/modules.conf?).
Marc
remote client failures
I am having problems backing up a client in different building (on a different subnet). The strange thing is this worked for over a year and suddenly started failing. It does not appear to be an acl or firewall issues, because sometimes it will work. I set up a separate config just for this host so I could test, and find that I can kick of amdump, it appears to start on the client (I get the debug files), but at some point it dies and I get an amandad debug with the following that the end: amandad: time 126.413: dgram_recv: timeout after 10 seconds amandad: time 126.413: waiting for ack: timeout, retrying amandad: time 136.413: dgram_recv: timeout after 10 seconds amandad: time 136.413: waiting for ack: timeout, retrying amandad: time 146.413: dgram_recv: timeout after 10 seconds amandad: time 146.413: waiting for ack: timeout, retrying amandad: time 156.413: dgram_recv: timeout after 10 seconds amandad: time 156.413: waiting for ack: timeout, retrying amandad: time 166.413: dgram_recv: timeout after 10 seconds amandad: time 166.413: waiting for ack: timeout, giving up! amandad: time 166.413: pid 6926 finish time Wed Sep 22 10:04:29 2004 If I stop the processes on the server, and run amcleanup, and restart amdump, with _no_ changes to anything, the dump will complete normally, most of the time. Other times it will fail with the same type of output in the debug file and I'll have to repeat. The client and server are running linux, (debian testing) amanda 2.4.4.p3. Needless to say, the intermittancy of this making troubleshooting difficult. The clients on the same subnet as the server back up normally. -- George Kelbley System Support Group Computer Science Department University of New Mexico 505-277-6502Fax: 505-277-6927
Short writes/SCSI errors?
I'm trying to get Amanda working with a Sony TSL-A300C AIT-1 autoloader (SCSI-based), but not having much luck. The tape drive and the robot are detected by the kernel and I can send mt(1) commands to the drive just fine: scsi0: scanning scsi channel 5 [P1] for physical devices. Vendor: SONY Model: TSL-A300C Rev: L202 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: SONY Model: TSL-A300C Rev: L202 Type: Medium Changer ANSI SCSI revision: 02 Attached scsi generic sg2 at scsi0, channel 5, id 4, lun 0, type 1 Attached scsi generic sg3 at scsi0, channel 5, id 4, lun 1, type 8 st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 5, id 4, lun 0 st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575 st0: Block limits 2 - 16777215 bytes. However, I can't seem to write a tape. amtapetype says: Estimate phase 1...amtapetype: could not write any data in this pass: short write and kernel dmesg output says: st0: Error 400f0 (sugg. bt 0x0, driver bt 0x0, host bt 0x4). st0: Error 4000c (sugg. bt 0x0, driver bt 0x0, host bt 0x4). And if I try to write a tape directly with tar(1), I get: [EMAIL PROTECTED]:pts/0 /home/jwm# tar cvf /dev/nst0 . ./ ./.bashrc ./.bash_profile ./.bash_history tar: /dev/nst0: Wrote only 0 of 10240 bytes tar: Error is not recoverable: exiting now and dmesg says: st0: Error 400f0 (sugg. bt 0x0, driver bt 0x0, host bt 0x4). st0: Error 4000c (sugg. bt 0x0, driver bt 0x0, host bt 0x4). st0: Error on write filemark. The SCSI chain is properly terminated AFAICT, and the autoloader is the only thing attached to that channel. Am I missing something, or do I have a dead unit? thanks, john -- John Morrissey _o/\ __o [EMAIL PROTECTED]_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__
TAPE
(excuse me for my bad english) I have 2 tapes: Quantum Super DLT 320 HP DDS-3 4MM DAT connected to Sun Enterprise 250 Are these tapes compatible with Amanda? I can´t find information about that. Leandro Argentina.
Re: TAPE
On Wed, Sep 22, 2004 at 04:47:06PM -0300, Leandro wrote: I have 2 tapes: Quantum Super DLT 320 HP DDS-3 4MM DAT connected to Sun Enterprise 250 Are these tapes compatible with Amanda? I can't find information about that. Generally speaking, if your OS supports the drives, Amanda does.
Re: TAPE
On Wed, Sep 22, 2004 at 04:47:06PM -0300, Leandro wrote: (excuse me for my bad english) I have 2 tapes: Quantum Super DLT 320 HP DDS-3 4MM DAT connected to Sun Enterprise 250 Are these tapes compatible with Amanda? I can´t find information about that. If programs like dd, tar (the gnu version, not Sun's), ufsdump can write to your drives, amanda can use them. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
TAPE
My Sun Solaris 7 can use tapes without problems. I compile lastest amanda stable ok. I don´t know how install webmin-amanda module. Is there otherGUI for Amanda ?
Amdump keeps running
appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
# index yes
# record no
define dumptype always-full {
comment Full dump of this filesystem always
index yes
compress none
priority high
dumpcycle 1 days # AMANDA_WEBMIN
}
# network interfaces
#
# These are referred to by the disklist file. They define the attributes
# of the network interface that the remote machine is accessed through.
# Notes: - netusage above defines the attributes that are used when the
# disklist entry doesn't specify otherwise.
#- the values below are only samples.
#- specifying an interface does not force the traffic to pass
# through that interface. Your OS routing tables do that. This
# is just a mechanism to stop Amanda trashing your network.
# Attributes are:
# use - bandwidth above which amanda won't start
# backups using this interface. Note that if
# a single backup will take more than that,
# amanda won't try to make it run slower!
define interface local {
comment a local disk
use 1000 kbps
}
define interface eth0 {
comment 10 Mbps ethernet
use 400 kbps
}
# You may include other amanda configuration files, so you can share
# dumptypes, tapetypes and interface definitions among several
# configurations.
#includefile /usr/local/amanda.conf.main
[EMAIL PROTECTED] root]#
[EMAIL PROTECTED] root]# more /etc/amanda/DailySet1/disklist
stanger.interlinc.net /dev/hda2 always-full -1 local
[EMAIL PROTECTED] root]#
[EMAIL PROTECTED] root]# more /var/lib/amanda/DailySet1/log.20040922.5
DISK planner stanger.interlinc.net /dev/hda2
START planner date 20040922
INFO planner Adding new disk stanger.interlinc.net:/dev/hda2.
START driver date 20040922
START taper datestamp 20040922 label DailySet13 tape 0
FINISH planner date 20040922
STATS driver startup time 70.775
INFO taper tape DailySet13 kb 448 fm 1 writing file: Input/output error
FAIL taper stanger.interlinc.net /dev/hda2 20040922 0 [out of tape]
ERROR taper no-tape [[writing file: Input/output error]]
[EMAIL PROTECTED] root]#
Re: Amdump keeps running
On Wed, Sep 22, 2004 at 04:37:28PM -0500, Jason Miller wrote:
Hello all, I am new to the amanda world and have setup a redhat 9.0 box
with Amanda from PRM. I have a Dell Powervault 122T. When I run a amdump it
estimates the size correctly, which is 23Gigs it hits 100% then keeps going
instead of backing it up to the tape. Anyone have any ideas what could be
causing the problem? I am pasting my configs for your review. As I said I am
green on this product and I am sure I missed something along the way but am
way too stupid to figure it out.
[EMAIL PROTECTED] root]# more /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: BNCHMARK Model: VS640Rev: 5639
Type: Sequential-AccessANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: BNCHMARK Model: VS640Rev: 5639
Type: Medium Changer ANSI SCSI revision: 02
VS640 sounds like 8 tapes of VS80 type, about 40GB uncompressed.
tapetype pv120T-dds4 # AMANDA_WEBMIN
dds4 sounds like a DAT 4, about 20GB uncompressed
# [EMAIL PROTECTED]
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype pv120T-dds4 {
comment Dell PowerVault 122T DLT 8 tape autoloader
Well, now is it VS80, DDS4, or DLT8???
length 8 mbytes
In any event, I don't think the actual capacity, uncompressed, is 80GB.
[EMAIL PROTECTED] root]# more /etc/amanda/DailySet1/disklist
stanger.interlinc.net /dev/hda2 always-full -1 local
[EMAIL PROTECTED] root]#
[EMAIL PROTECTED] root]# more /var/lib/amanda/DailySet1/log.20040922.5
DISK planner stanger.interlinc.net /dev/hda2
START planner date 20040922
INFO planner Adding new disk stanger.interlinc.net:/dev/hda2.
START driver date 20040922
START taper datestamp 20040922 label DailySet13 tape 0
FINISH planner date 20040922
STATS driver startup time 70.775
INFO taper tape DailySet13 kb 448 fm 1 writing file: Input/output error
It wrote 1 file (fm 1) and about 448KB successfully. That file was the
amanda tape header, not a backup dump. Then it hit an error.
FAIL taper stanger.interlinc.net /dev/hda2 20040922 0 [out of tape]
ERROR taper no-tape [[writing file: Input/output error]]
It says out of tape, but consider other possibilities.
Amanda gets an error from the system that often means one of
several possibilities. Amanda then lists a likely reason.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amdump keeps running
I changed the two lines that have TapeType in them to unknown-tapetype from
a copy/paste from the FQ on amanda's site. It is in fact a Powervault 122T
DLT VS80, forgot to put the config back to the way I have had it. I edited
it to see if it made a difference and of course it didn't.
tapetype unknown-tapetype # AMANDA_WEBMIN
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 34500 mbytes
filemark 10 kbytes
speed 1291 kps
}
From: Jon LaBadie [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Wed, 22 Sep 2004 18:15:34 -0400
To: [EMAIL PROTECTED]
Subject: Re: Amdump keeps running
On Wed, Sep 22, 2004 at 04:37:28PM -0500, Jason Miller wrote:
Hello all, I am new to the amanda world and have setup a redhat 9.0 box
with Amanda from PRM. I have a Dell Powervault 122T. When I run a amdump it
estimates the size correctly, which is 23Gigs it hits 100% then keeps going
instead of backing it up to the tape. Anyone have any ideas what could be
causing the problem? I am pasting my configs for your review. As I said I am
green on this product and I am sure I missed something along the way but am
way too stupid to figure it out.
[EMAIL PROTECTED] root]# more /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: BNCHMARK Model: VS640Rev: 5639
Type: Sequential-AccessANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: BNCHMARK Model: VS640Rev: 5639
Type: Medium Changer ANSI SCSI revision: 02
VS640 sounds like 8 tapes of VS80 type, about 40GB uncompressed.
tapetype pv120T-dds4 # AMANDA_WEBMIN
dds4 sounds like a DAT 4, about 20GB uncompressed
# [EMAIL PROTECTED]
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype pv120T-dds4 {
comment Dell PowerVault 122T DLT 8 tape autoloader
Well, now is it VS80, DDS4, or DLT8???
length 8 mbytes
In any event, I don't think the actual capacity, uncompressed, is 80GB.
[EMAIL PROTECTED] root]# more /etc/amanda/DailySet1/disklist
stanger.interlinc.net /dev/hda2 always-full -1 local
[EMAIL PROTECTED] root]#
[EMAIL PROTECTED] root]# more /var/lib/amanda/DailySet1/log.20040922.5
DISK planner stanger.interlinc.net /dev/hda2
START planner date 20040922
INFO planner Adding new disk stanger.interlinc.net:/dev/hda2.
START driver date 20040922
START taper datestamp 20040922 label DailySet13 tape 0
FINISH planner date 20040922
STATS driver startup time 70.775
INFO taper tape DailySet13 kb 448 fm 1 writing file: Input/output error
It wrote 1 file (fm 1) and about 448KB successfully. That file was the
amanda tape header, not a backup dump. Then it hit an error.
FAIL taper stanger.interlinc.net /dev/hda2 20040922 0 [out of tape]
ERROR taper no-tape [[writing file: Input/output error]]
It says out of tape, but consider other possibilities.
Amanda gets an error from the system that often means one of
several possibilities. Amanda then lists a likely reason.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: remote client failures
George: See if someone in your Network team changed anything in your firewall that would affect timeouts for UDP traffic. It appears to me that the amandad is not seeing the messages in time and timing out. Someone may have shortened a timeout value in the firewall or fat-fingered a setting that affects your connection. You may have already checked these items; if so, sorry to duplicate your efforts, otherwise, look at network changes that occur between the two servers. Best wishes, Donald L. (Don) Ritchey Information Technology Exelon Corporation -Original Message- From: George Kelbley [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 22, 2004 11:20 AM To: [EMAIL PROTECTED] Subject: remote client failures I am having problems backing up a client in different building (on a different subnet). The strange thing is this worked for over a year and suddenly started failing. It does not appear to be an acl or firewall issues, because sometimes it will work. I set up a separate config just for this host so I could test, and find that I can kick of amdump, it appears to start on the client (I get the debug files), but at some point it dies and I get an amandad debug with the following that the end: amandad: time 126.413: dgram_recv: timeout after 10 seconds amandad: time 126.413: waiting for ack: timeout, retrying amandad: time 136.413: dgram_recv: timeout after 10 seconds amandad: time 136.413: waiting for ack: timeout, retrying amandad: time 146.413: dgram_recv: timeout after 10 seconds amandad: time 146.413: waiting for ack: timeout, retrying amandad: time 156.413: dgram_recv: timeout after 10 seconds amandad: time 156.413: waiting for ack: timeout, retrying amandad: time 166.413: dgram_recv: timeout after 10 seconds amandad: time 166.413: waiting for ack: timeout, giving up! amandad: time 166.413: pid 6926 finish time Wed Sep 22 10:04:29 2004 If I stop the processes on the server, and run amcleanup, and restart amdump, with _no_ changes to anything, the dump will complete normally, most of the time. Other times it will fail with the same type of output in the debug file and I'll have to repeat. The client and server are running linux, (debian testing) amanda 2.4.4.p3. Needless to say, the intermittancy of this making troubleshooting difficult. The clients on the same subnet as the server back up normally. -- George Kelbley System Support Group Computer Science Department University of New Mexico 505-277-6502Fax: 505-277-6927 This e-mail and any of its attachments may contain Exelon Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Exelon Corporation family of Companies. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You.
Re: TAPE
On Wednesday 22 September 2004 15:47, Leandro wrote: (excuse me for my bad english) I have 2 tapes: I asume you mean tape drives below Quantum Super DLT 320 HP DDS-3 4MM DAT Both should be able to be used unless the Quantum somehow has a broken scsi protocol, which isn't likely. connected to Sun Enterprise 250 Are these tapes compatible with Amanda? I can´t find information about that. Consult your equ to dmesg and see what device it was found at when the machine was last booted. Then, using mt, check that device and see if you can control a tape inserted into those drives. Ditto the changer if there is one, using mtx this time. If mt works with the quantum, the rewind the tape in it, and fire off a session of amtapetype -f /dev/whatever -e known size of drive, this will get the true capacity of the drive. But... Turn off any hardware compression first else amtapetype will probably complain, and return a tapesize thats obviously smaller that the rated size of the tape with compression turned off. The data src while testing is /dev/urandom, and that will expand in a hardware compressor by 5-15% instead of being shrunk. In any event, amtapetype will probably take several hours to run as it does two, till the tape is full, writes. Don't use a tape with something precious on it. Leandro Argentina. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: TAPE
On Wednesday 22 September 2004 17:03, Leandro wrote: My Sun Solaris 7 can use tapes without problems. I compile lastest amanda stable ok. I don´t know how install webmin-amanda module. Is there other GUI for Amanda ? No. There has been mention of I'm gonna write one at about 90 day intervals for years but no one has that I'm aware of. Amanda's design framework is done with the view that it should be a cron job, running in the middle of the night unmolested, and you don't need a gui for that. It emails you any results it might generate, so you pretty much know what amanda is doing. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Quantum VS80, VS160, SDLT320, LTO-1, LTO-2
I'm going to purchase a Quantum ValueLoader which offers options of using DLT VS80, VS160, SDLT320, LTO-1 and LTO-2. Can those who has succeeded in any of them give me a yell. Thanks! Alan
