Read Me
samdrives is a tool for monitoring and managing tape drives on multiple
SAM/QFS metadata servers. samdrives(1) is a curses(3) based program
that polls samdrivesd(8) running on the metadata servers to collect
both SAM/QFS status about tape drives, and I/O performance data
about the tape drives (similar to what iostat(1) displayss). It also supports
remote execution of some SAM/QFS commands on the metadata servers
("samd start", "samd stop", "samcmd idle/on EQ", "samcmd aridle",
"samcmd arrun").
INSTALLATION
Edit Makefile and change TOPDIR (and other defines if needed) to the
location where you want to install samdrives. Note in version 5 of
SAM/QFS a new function sam_devstatl(3) was introduced to support
tape drives whose capacity exceeded 32 bits, obsoleting previous
functions sam_devstat(3) and sam_ndevstat(3). It appears the #define
DT_OSD_MASK first appears in version 5, so this is used in the
conditional compilation directives to choose sam_devstatl(3) or
sam_ndevstat(3).
make
make install
The daemon samdrivesd(8) needs to run on any metadata servers that you
wish to manage with samdrives, the boot script samdrives.boot is provided
if you wish to use it to start samdrivesd at boot time. It should be
installed in /etc/init.d, and the following symlinks should be made, on each
metadata server that should run samdrivesd(8):
ln -s /etc/init.d/samdrives.boot /etc/rc0.d/K99samdrives.boot
ln -s /etc/init.d/samdrives.boot /etc/rc1.d/K99samdrives.boot
ln -s /etc/init.d/samdrives.boot /etc/rc2.d/K99samdrives.boot
ln -s /etc/init.d/samdrives.boot /etc/rc2.d/S99samdrives.boot
CONFIGURATION
samdrivesd(8) needs to be configured as to which hosts and users are
allowed to read and/or modify tape drive status. The configuration
file samdrivesd.conf (located in TOPDIR/conf) is read at start time
and if a HUP signal is received. See the man page samdrivesd(8) for
details, a sample configuration might be:
host myhost:trusted
user myusername:admin
user operator
group sysadmin
This configuration specifies that only users on "myhost" can connect to
samdrivesd. The user "myusername" has admin privileges (ie can execute
commands that change drive status, eg "idle", "on", "aridle" ...). The
user operator and anyone in group sysadmin are allowed to read drive status
but not change it.
samdrives(1) needs to know what metadata servers to contact samdrivesd(8)
on, it does this in 2 ways. It will read samdrives.conf
(located in TOPDIR/conf) for a list of metadata server hostnames, and/or
it will attempt to read all of the hosts.xxx files in /etc/opt/SUNWsamfs
if they exist (it looks for lines that have the keyword "server").