problems with tape drive?

2002-09-02 Thread chris-amanda 

Hi all,

I'm having some grief with a tape drive that starts backing up, but gets an
error and terminates... In /var/log/messages I see:

Aug 29 22:15:00 osiris kernel: PCI: Enabling device 00:0f.0 (0006 -> 0007)
Aug 29 22:15:00 osiris kernel: PCI: Enabling device 00:0f.1 (0006 -> 0007)
Aug 29 22:15:00 osiris kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.4
Aug 29 22:15:00 osiris kernel: 
Aug 29 22:15:00 osiris kernel: aic7899: Ultra160 Wide Channel A,
SCSI Id=7, 32/253 SCBs
Aug 29 22:15:00 osiris kernel:
Aug 29 22:15:00 osiris kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.4
Aug 29 22:15:00 osiris kernel: 
Aug 29 22:15:00 osiris kernel: aic7899: Ultra160 Wide Channel B,
SCSI Id=7, 32/253 SCBs
Aug 29 22:15:00 osiris kernel:
Aug 29 22:15:15 osiris kernel:   Vendor: SONY  Model: SDT-1
Rev: 0110
Aug 29 22:15:15 osiris kernel:   Type:   Sequential-Access
ANSI SCSI revision: 02
Aug 29 22:15:15 osiris kernel: (scsi0:A:2): 40.000MB/s transfers (20.000MHz,
offset 15, 16bit)
Aug 29 22:15:22 osiris kernel: st: Version 20020205, bufsize 32768, wrt
30720, max init. bufs 4, s/g segs 16
Aug 29 22:15:22 osiris kernel: Attached scsi tape st0 at scsi0, channel 0,
id 2, lun 0
Aug 29 22:15:22 osiris kernel: st0: Block limits 1 - 16777215 bytes.
Aug 30 01:46:03 osiris kernel: st0: Error on write filemark.
Aug 30 02:00:00 osiris kernel: scsi : 0 hosts left.
Aug 30 02:00:00 osiris kernel: st: Unloaded.

And in the backup report:

These dumps were to tape eng-au002.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: eng-au003.

FAILURE AND STRANGE DUMP SUMMARY:
  osiris /dev/hda3 lev 0 FAILED [out of tape]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:14
Dump Time (hrs:min)0:11   0:00   0:11
Output Size (meg) 298.64.7  294.0
Original Size (meg)   889.0   19.5  869.5
Avg Compressed Size (%)33.6   23.9   33.8   (level:#disks ...)
Filesystems Dumped3  1  2   (1:2)
Avg Dump Rate (k/s)   447.8  650.0  445.7

Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0
Avg Tp Write Rate (k/s) -- -- --


NOTES:
  planner: Full dump of osiris:/dev/hda3 promoted from 2 days ahead.
  planner: Full dump of osiris:/dev/hda1 promoted from 2 days ahead.
  taper: tape eng-au002 kb 0 fm 0 writing filemark: Input/output error
  driver: going into degraded mode because of tape error.


DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
osiris   /dev/hda1   1 899352  39.2   0:13  26.3   N/A   N/A
osiris   /dev/hda3   0   19943   4768  23.9   0:07 650.0   N/A   N/A
osiris   /dev/hdb1   1  889470 300672  33.8  11:02 454.1   N/A   N/A

(brought to you by Amanda version 2.4.2p2)


--

The /dev/hdb1 file is in the holding disk, but if I try and flush it, it'll
fail again.

in /var/log/amanda/amdump.1 (snipped):

driver: result time 140.611 from dumper0: DONE 00-1 19943 4768 7 [sec
7.335 kb 4768 kps 650.0 orig-kb 19943]
driver: finished-cmd time 140.647 dumper0 dumped osiris:/dev/hda3
driver: send-cmd time 140.647 to taper: FILE-WRITE 00-2
/backup/20020902/osiris._dev_hda3.0 osiris /dev/hda3 0 20020902
driver: state time 140.647 free kps: 3400 space: 27266580 taper: writing
idle-dumpers: 4 qlen tapeq: 0 runq: 2 roomq: 0 wakeup: 7 driver-idle:
start-wait
driver: interface-state time 140.647 if : free 2000 if LE0: free 400 if
LOCAL: free 1000
driver: hdisk-state time 140.647 hdisk 0: free 27266580 dumpers 0
taper: writing end marker. [eng-au002 ERR kb 0 fm 0]
driver: result time 140.654 from taper: TAPE-ERROR 00-2 [writing
filemark: Input/output error]
driver: finished-cmd time 140.654 taper wrote osiris:/dev/hda3
dump of driver schedule before start degraded mode:

  osiris /dev/hda1 lv 0 t   180 s   295648 p 0
  osiris /dev/hdb1 lv 1 t   638 s   310080 p 2

dump of driver schedule after start degraded mode:

  osiris /dev/hdb1 lv 1 t   638 s   310080 p 2
  osiris /dev/hda1 lv 1 t 8 s  342 p 0

driver: state time 140.654 free kps: 3400 space: 27266580 taper: DOWN
idle-dumpers: 4 qlen tapeq: 0 runq: 2 roomq: 0 wakeup: 7 driver-idle:
start-wait

RE: Question about /home/amanda/20020904/ directory

2002-09-04 Thread chris-amanda 

yes, or it may be a dump left over from an incomplete backup (i.e. one that
didn't get written to tape).

If you notice that you have several of these, and they actually contain
data:

su amanda
cd ~amanda/
du ./* -sh

this will tell you how big the directories are. If they're empty I delete
them. If they actually contain something, I then run amflush:

amflush myconf

and stick in the next tape that it wants.

Cheers,

Crhis

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Martinez, Michael -
|CSREES/ISTM
|Sent: Wednesday, 4 September 2002 22:35
|To: [EMAIL PROTECTED]
|Subject: Question about /home/amanda/20020904/ directory
|
|
|Is the /home/amanda/20020904/ (or whatever date on a particular day)
|directory a temporary directory used by amanda during the
|backup process?
|
|I had never noticed these directories before, until a couple days ago.
|
|Michael Martinez
|System Administrator
|Information Systems and Technology Management
|CSREES - United States Department of Agriculture
|(202) 720-6223
|

RE: problems with tape drive?

2002-10-11 Thread chris-amanda 
Hi Chris,

I tried this, and afterwards it no longer reads any tapes at all. Tried
powering off the server, turning on again - no luck. Have placed a service
call to get the drive replaced, so will let you know what happens.

Cheers,

Chris

|-Original Message-
|From: Christoph Scheeder [mailto:christoph.scheeder@;scheeder.de]
|Sent: Tuesday, 3 September 2002 17:10
|To: [EMAIL PROTECTED]
|Cc: amanda Mailingliste
|Subject: Re: problems with tape drive?
|
|
|Hi,
|your problem is the fixed hardware-blocksize of the SDT-1,
|i had the same problem with my SDT-9000 and solve it by switching
|it to variable blocksize using
|
|mt setblk 0
|
|after each reset as the tapedevice switches back to the fixed default
|block-size after every reset.
|Christoph
|
|