Clonfs
RAID subsystem: SUN StorEdge 3510FC.
Upper unit s/n: 1094MIL-052708764D, f/n: F46973.
Lower unit s/n: 1094MIL-0521087898, f/n: F46974.
NOTE: on April 23, 2010 both power supplies on bottom unit went off; Paul Letta unplugged both cords, flip switches, they came back. It may be not the first time. Execise that procedure if raid goes down again.
Console access:
telnet clonfs password: usual su password
Mount: it is mounted on clondaq2 only as ZFS file system.
Move2SILO
Set of scripts was developed by Mike Johnson to manage data moving from RAID to SILO. It was modified by Vladimir Sapunenko and later by Sergey Boyarinov to accomodate new hardware. Current version resides in /usr/local/src/raid on Opteron Solaris machines, including README with logic description, and following document has more information: (PowerPoint, HTML, pdf).
CUE directory /w/mss must be mounted and link /mss -> /w/mss must be created.
Work area for the procedure is /ssa. File /ssa/ENVIRONMENT contains some environment definitions including list of raid partitions, it must be modified if partitions added, removed or renamed. File /ssa/STUB.TARGET contains directory name on SILO where data will be moved, it must be modified before every run period, and Computer Center must be asked to create appropriate directory on SILO.
Procedure will be activated every time when Event Recorder opens new file. Event Recorder calles script checkdisk which calls script usr/local/src/raid/checkraid and procedure starts. It will send a page and email in case of trouble. Data can be moved manually using script clonput2 provided by Computer Center (Bryan Hess) and stored along with other scripts, for example do following as root (or as clasrun through sudo):
clonput2 /mnt/raid1/stage_in/clas_012345.* /mss/clas/e99/data
Please note that software provided by Computer Center's is machine dependent. It resides in usr/local/mss and currently supports Linux and Opteron Solaris. Sparc Solaris was supported in the past but currently turned off because we are not running Event Recorder there.
NOTE: Sudo must be configured to run scripts from clasrun account.