Re: Can't do amlabel

2003-06-16 Thread Junaidi 
On Monday 16 June 2003 15:18, Paul Bijnens wrote:
 Junaidi wrote:
  i'm currently stuck. I cant do any backup, amcheck says it's not an
  amanda tape. I tried to label the tape but amlabel says that the label is
  already on the tape. So i did a amrmtape. Now i'm having trouble
  labelling the tape again. These tapes have been used before for amanda..
  abt six mths ago, so now i'm doing a new installation, that's why the
  labels are still there.
 
  This is my dmesg
 
  blk: queue f7e16e18, I/O limit 4095Mb (mask 0x)
Vendor: BNCHMARK  Model: DLT1  Rev: 5032
Type:   Sequential-Access  ANSI SCSI revision: 02
  blk: queue c8eaa218, I/O limit 4095Mb (mask 0x)
  (scsi0:A:5): 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
  Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0

 What is the output of mt -f /dev/nst0 status?

luke root # mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x40 (DLT1 40 GB, or Ultrium).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN


  [EMAIL PROTECTED] amanda $ amlabel tuesday tuesday2
  amlabel: label tuesday2 already on a tape

 That's because amanda has this tape in the tapelist file, the file
 that contains all the tape(-label)s and dates when last used.
 This file is consulted to tell you which tape is expected next.

  
  [EMAIL PROTECTED] tuesday $ amrmtape tuesday tuesday2
  amrmtape: preserving original database in curinfo.orig.28037 (exported).
 
  
  [EMAIL PROTECTED] tuesday $ amlabel tuesday tuesday2
  rewinding, reading label, not an amanda tape
  rewinding, writing label tuesday2, checking label
  amlabel: no label found, are you sure /dev/nst0 is non-rewinding?

 So amanda relabeled the tape, but when checking if it wrote it
 correctly, it failed.  You have to find out why that is.
 Bad tape?  Wrong blocksize?  Bad karma?

Bad tape i doubt, i have abt 30 tapes.. so far i have tested abt 5 tapes.. 
they can't be all bad. On my mt status it says Tape block size 0 bytes , 
should i do a setblk? Anyway i did. Here's the output.

[EMAIL PROTECTED] amanda $ mt -f /dev/nst0 tell
At block 1.
[EMAIL PROTECTED] amanda $ mt -f /dev/nst0 setblk 512
/dev/nst0: Input/output error

Please please dont let it be bad karma, tell me i got it wrong somewhere.

Can't do amlabel

2003-06-15 Thread Junaidi 
Hello,

i'm currently stuck. I cant do any backup, amcheck says it's not an amanda 
tape. I tried to label the tape but amlabel says that the label is already on 
the tape. So i did a amrmtape. Now i'm having trouble labelling the tape 
again. These tapes have been used before for amanda.. abt six mths ago, so 
now i'm doing a new installation, that's why the labels are still there.

This is my dmesg

blk: queue f7e16e18, I/O limit 4095Mb (mask 0x)
  Vendor: BNCHMARK  Model: DLT1  Rev: 5032
  Type:   Sequential-Access  ANSI SCSI revision: 02
blk: queue c8eaa218, I/O limit 4095Mb (mask 0x)
(scsi0:A:5): 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0

My tapetype.
define tapetype daily {
comment just produced by tapetype program
length 34798 mbytes
filemark 152 kbytes
speed 2578 kbytes
}


[EMAIL PROTECTED] amanda $ amcheck tuesday
Amanda Tape Server Host Check
-
Holding disk /backup: 9092960 KB disk space available, that's plenty
ERROR: /dev/nst0: not an amanda tape
   (expecting a new tape)
NOTE: skipping tape-writable test
Server check took 5.045 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.226 seconds, 0 problems found

(brought to you by Amanda 2.4.4)
+++
[EMAIL PROTECTED] amanda $ amlabel tuesday tuesday2
amlabel: label tuesday2 already on a tape


[EMAIL PROTECTED] tuesday $ amrmtape tuesday tuesday2
amrmtape: preserving original database in curinfo.orig.28037 (exported).


[EMAIL PROTECTED] tuesday $ amlabel tuesday tuesday2
rewinding, reading label, not an amanda tape
rewinding, writing label tuesday2, checking label
amlabel: no label found, are you sure /dev/nst0 is non-rewinding?

Re: gtar - sendsize reports no size

2002-05-22 Thread junaidi 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


 sendsize.20020522155439.debug
  ...removed...
 calculating for amname '/usr', dirname '/usr'
 sendsize: getting size via gnutar for /usr level 0
 opening /usr/local/var/amanda/gnutar-lists/bdback.fnal.gov_usr_0.new:
  No such file or directory
 calculating for amname '/var', dirname '/var'



I'm pretty new to amanda but my guess is that you need to have 
/usr/local/var/amanda/gnutar-lists on your amanda client.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE87ESUInIYkBVpGqURAloiAJ4wWfBjQRsFLDWJE6dMWQLOW1uBmACeOGC4
7WfAKMp0o+25sgk4Me/j1yE=
=GNqO
-END PGP SIGNATURE-