On Tue, Sep 19, 2006 at 02:13:55PM +1000, Craig Dewick wrote:
> 
> On Mon, 18 Sep 2006, Jon LaBadie wrote:
> 
> >It won't be the script that sets up specific devices.  The OS picks
> >the device names based on its scans and distorted logic.  In case
> >you are not familiar with that naming scheme c1t2d3 would be
> > "c"ontroller number 1       (you may have multiple scsi, or ide+scsi or?)
> > "t"arget     number 2       (aka scsi id or disk number for ide)
> > "d"evice     number 3 (aka scsi lun)
> >
> >So you need to setup your st.conf and sgen.conf (tape drive and changer
> >respectively) and do a config reboot (or devfsadm while testing, but
> >I recommend a reboot at the end to be certain).  Then find which device
> >names were assigned to your devices.
> 
> Yes I've done a re-config boot, but just to be sure I'll do another one 
> and report back on any differences in software behaviour.
> 
> >For this exploration don't use amanda.  Use mtx for changer explore and
> >testing and mt/tar/dd for drive explore and testing.
> 
> Yep I was using mtx to try and manipulate the changer, then I decided to 
> try out amtape and see if it made a difference.

Craig,

amtape is held together by the same chg-mtx glue that allows
amdump to work, if you don't have mtx working all of the other
utilities, which ride on top of it, will also fail.

Brian



Reply via email to