uec / Issue.Tracker

Automatically exported from code.google.com/p/usc-epigenome-center
0 stars 0 forks source link

cleaning up gastorage2 #815

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
To free up space on gastorage2, you may need to remove old cifs.

I usually do it by month, to see if the cifs have been removed for july 2014:
login root
cd /bigpool/slxa/incoming
find 1407*/Data/Intensities/L00?/ -name *.cif

Possibility #1
a big list of cifs show up:
140702_SN550_0407_AC4YC8ACXX/Data/Intensities/L001/C56.1/s_1_1308.cif
140702_SN550_0407_AC4YC8ACXX/Data/Intensities/L001/C56.1/s_1_1306.cif
140702_SN550_0407_AC4YC8ACXX/Data/Intensities/L001/C56.1/s_1_2213.cif
140702_SN550_0407_AC4YC8ACXX/Data/Intensities/L001/C56.1/s_1_2104.cif

so we know cifs are still present, no need to continue,  go ahead and ctrl-c to 
stop finding. we have confirmed that july 2014 needs cleaning.

Possibility #2:
if the command just hangs with no output for a more then 10 seconds, it means 
it's searching for cifs and can't find any. You can terminate the cmd with 
ctrl-c, you have confirmed that cifs have already been removed for this month.

if you have confirmed that cifs are present (Possibility #1), then you can now 
delete them. the cmd is very similar except we at another flag to the find cmd
cd /bigpool/slxa/incoming
find 1407*/Data/Intensities/L00?/ -name *.cif -exec rm {} \; 

this cmd will find all cifs, and then execute the cmd "rm" on it. It may take 
some time since there are many cifs.
you have now cleaned up all cifs for the specified month.

Original issue reported on code.google.com by zack...@gmail.com on 24 Sep 2014 at 8:16