[Halld-online] [New Logentry] Switched to /gluonraid2

[davidl at jlab.org]

Logentry Text:
--
We switched to using the second RAID disk /gluonraid2 since with the increased event rate and large mode 8 data volume /gluonraid1 was nearly full. Some note on what was needed are below. Most of this needs to be automated, but will need to be coupled into the DAQ system, and the auto-deleting algorithm for clearing out older files on the disk.

***** Note that this means the Event Recorder is now running on gluonraid2 *****

Switching RAID disks

1. Make sure the following exist:

/raid/rawdata/volatile/$RUN_PERIOD/
/raid/rawdata/active/$RUN_PERIOD/rawdata
/raid/rawdata/staging/$RUN_PERIOD/rawdata
/raid/monitoring/conditions
/raid/monitoring/root

2. Edit $DAQ_HOME/config/hd_all/hosts so that the ER is run on the new raid disk
n.b. if configuration other than hd_all.XXX is being used, then that hosts file needs
to be updated.

3. Stop the following process on the old raid disk and start it on the new one. This is
what reports to EPICS the available disk space so that it can alarm.

$DAQ_HOME/tools/raidutils/hd_raidmonitor.py

4. Make sure the crontab on the new raid disk is setup to run the stage_to_tape script.
The crontabs can be found in /gluex/etc/crontabs . These are backed up in svn so make
sure any modifications are checked in.

5. Replace link /gluex/raid to point to the new raid disk


---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/3313553
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.jlab.org/pipermail/halld-online/attachments/20141213/a64a2046/attachment.html