Data handling scripts (to MSS and deletion)

Hall A:

Data are moved to MSS and deleted from the ADAQ disks using a cron job that runs on adaqeb1, adaqeb2, and adaqeb3. Login as the adaq account and type "crontab -l" to see what it is. /adaqfs/home/adaq/jmirror_scripts/adaqeb_sbs_jmirror

At the heart of the script is the JLAB-standard "jmirror" script.

Hall C:

A similar jmirror-based script runs under cron on coda@cdaql5 /home/coda/coda/jmirror_scripts/hallc_jmirror

There are also scripts that check for anomolies in the process. You can find these also under cron.

[adaq@adaq1 ~]$ crontab -l

[coda@cdaql5 ~]$ crontab -l

For most users, the main rule is this : DON'T INTERFERE ! Please do not delete, move, or rename raw data files. Especially do not delete anything ! The risk is doing a "rm" command which wipes out weeks of precious beam time. Well, that's very unlikely to happen because we copy promptly but the possibility exists. Please have the self-discipline to not "rm" from a "data" disk. Also, please do not put any files on a disk with the string "data" on the name of the disk partition, e.g. /adaq1/data1. Those "data" disks are for raw data only. There are separate "work" disks and "scratch" disks for files that are not raw data, for example root output files. And those disks are not backed up.