Amanda-Users

Re: another chg-zd-mtx problem

2003-02-12 15:30:15
Subject: Re: another chg-zd-mtx problem
From: Jean-Louis Martineau <martinea AT IRO.UMontreal DOT CA>
To: Pete Poggione <ppoggione AT ebsllc DOT com>
Date: Wed, 12 Feb 2003 14:07:24 -0500
Hi Pete,

Could you try this patch.

Jean-Louis

On Wed, Feb 12, 2003 at 12:25:40PM -0500, Pete Poggione wrote:
> amcheck now gives me:
> 
> Amanda Tape Server Host Check
> -----------------------------
> Holding disk /var/tmp: 7048472 KB disk space available, that's plenty
> amcheck-server: could not get changer info: could not determine current
> slot
> 
> Amanda Backup Client Hosts Check
> --------------------------------
> Client check: 1 host checked in 0.556 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.3)
> 
> same if I try amtape. I get the 'could not determine current slot'
> error.
> 
> Incidentally there has been some questions as to the version of Amanda I
> am running. It's 2.4.3 now. I upgraded from 2.4.2 in hopes that it would
> fix the chg-zd-mtx problem.
> 
> The system is Mandrake 9.0
> 
> ~P
> 
> 
> On Wed, 2003-02-12 at 11:09, Eric Sproul wrote:
> > On Wed, 2003-02-12 at 10:49, Pete Poggione wrote:
> > > You and I are thinking the same. As I looked further it seems for some
> > > reason the target was not owned by root but rather by me.(?) changing
> > > the ownership to root eliminated all permission issues. It is now like
> > > this:
> > > 
> > > [root@ruby dev]# ls -l sg2
> > > lr-xr-xr-x    1 root     root           36 Feb 10 13:45 /dev/sg2 ->
> > > scsi/host0/bus0/target5/lun1/generic
> > > 
> > > [root@ruby lun1]# ls -l
> > > total 0
> > > crw-rw----    1 root     root      21,   2 Dec 31  1969 generic
> > 
> > Well, the mod date seems weird, in that it is set to the UNIX epoch, but
> > I guess that doesn't really matter.  It still doesn't appear that
> > amanda's group 'disk' would have access to this file, but that may be an
> > affect of your particular system (what OS is this?).  Your success with
> > mtx below means that for whatever reason, the permissions seem to be OK.
> > 
> > > mtx now responds correctly for user 'amanda'
> > > 
> > > [root@ruby amanda-2.4.3]# su amanda -c "mtx status"
> > >   Storage Changer /dev/changer:1 Drives, 6 Slots ( 0 Import/Export )
> > > Data Transfer Element 0:Full (Storage Element 1 Loaded)
> > >       Storage Element 1:Empty
> > >       Storage Element 2:Full 
> > >       Storage Element 3:Full 
> > >       Storage Element 4:Full 
> > >       Storage Element 5:Full 
> > >       Storage Element 6:Full 
> > > 
> > > Do you see anything weird about this or am I correct in assuming this
> > > should be ok?
> > 
> > This does indeed look like mtx succeeded.  The next step would be to
> > ensure that amanda can execute the changer functions via her generic
> > commands, like 'eject' or 'slot X'.  Something like
> > 
> > # su amanda -c amtape <config> slot 1
> > 
> > If that works, then you're all set.
> > 
> > Cheers,
> > Eric
> 

-- 
Jean-Louis Martineau             email: martineau AT IRO.UMontreal DOT CA 
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLE    Tel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7        Fax: (514) 343-5834

Attachment: chg-zd-mtx.sh.in.driveslot.diff
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>