Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7ed1e447413a5138-6aeec945-47944e20-bc5cb559-e01ae5ceba92be8ca8e4da1b"><ac:plain-text-body><![CDATA[

path

size [TB]

#files

Notes

]]></ac:plain-text-body></ac:structured-macro>

/glast/Data

785

807914

 

/glast/Data/Flight

767

792024

 

/glast/Data/Flight/Level1/

713

535635

670 TB registered in dataCat

/glast/mc

82

11343707

 

/glast/mc/ServiceChallenge/

56

6649775

 

/glast/Scratch

51

358511

~50 TB recovery possible

/glast/Data/Flight/Reprocess/

50

226757

~18 TB recovery possible

/glast/level0

13

2020329

 

/glast/bt

4

760384

 

/glast/test

2

2852

 

/glast/scratch

1

51412

 

/glast/mvmd5

0

738

 

/glast/admin

0

108

 

/glast/ASP

0

19072

 

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="856b1e7eb3e5206a-ab0f58a0-40e34dc2-b8b6b4e4-7e52a509c1a5b40c7f40fee7"><ac:plain-text-body><![CDATA[

path

size [GB]

#files

Notes

]]></ac:plain-text-body></ac:structured-macro>

/glast/Data/Flight/Reprocess/P120

22734

65557

potential production

/glast/Data/Flight/Reprocess/P110

14541

49165

removal candidate

/glast/Data/Flight/Reprocess/P106-LEO

8690

1025

 

/glast/Data/Flight/Reprocess/P90

3319

2004

removal candidate

/glast/Data/Flight/Reprocess/CREDataReprocessing

631

22331

 

/glast/Data/Flight/Reprocess/P115-LEO

533

1440

 

/glast/Data/Flight/Reprocess/P110-LEO

524

1393

removal candidate

/glast/Data/Flight/Reprocess/P120-LEO

503

627

potential production

/glast/Data/Flight/Reprocess/P105

264

33465

production

/glast/Data/Flight/Reprocess/P107

212

4523

 

/glast/Data/Flight/Reprocess/P116

109

25122

production

/glast/Data/Flight/Reprocess/Pass7-repro

22

16

removal candidate

/glast/Data/Flight/Reprocess/P100

8

20089

removal candidate

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3156b651534ff0ef-049f9d78-49474f68-b556abf8-d92da89fad9fdaca655f7d12"><ac:plain-text-body><![CDATA[

path

size [GB]

#files

Notes

]]></ac:plain-text-body></ac:structured-macro>

/glast/mc/ServiceChallenge

57458

6649775

 

/glast/mc/OpsSim

24691

4494890

 

/glast/mc/DC2

1818

136847

 

/glast/mc/OctoberTest

41

29895

 

/glast/mc/XrootTest

33

18723

removal candidate

/glast/mc/Test

14

13403

removal candidate

...

Filetype:

TotSize/#Runs =

Avg file size

(%)

RECON:

399257.600/13532 =

29.505 GiB

(58.2%)

CAL:

100147.200/13536 =

7.399 GiB

(14.6%)

SVAC:

71270.400/13535 =

5.266 GiB

(10.4%)

DIGI:

61542.400/13537 =

4.546 GiB

( 9.0%)

FASTMONTUPLE:

28262.400/13537 =

2.088 GiB

( 4.1%)

MERIT:

22528.000/13537 =

1.664 GiB

( 3.3%)

GCR:

676.800/13537 =

51.196 MiB

( 0.1%)

FASTMONTREND:

432.800/13537 =

32.739 MiB

( 0.1%)

DIGITREND:

337.100/13537 =

25.500 MiB

( 0.0%)

FILTEREDMERIT:

324.900/ 7306 =

45.538 MiB

( 0.0%)

MAGIC7HP:

244.700/13315 =

18.819 MiB

( 0.0%)

LS1:

183.700/13537 =

13.896 MiB

( 0.0%)

CALHIST:

181.400/13536 =

13.723 MiB

( 0.0%)

RECONTREND:

172.700/13537 =

13.064 MiB

( 0.0%)

TKRANALYSIS:

172.400/13536 =

13.042 MiB

( 0.0%)

LS3:

156.800/13537 =

11.861 MiB

( 0.0%)

RECONHIST:

124.400/13536 =

9.411 MiB

( 0.0%)

MAGIC7L1:

55.000/13315 =

4.230 MiB

( 0.0%)

FASTMONHIST:

53.400/13535 =

4.040 MiB

( 0.0%)

LS1BADGTI:

48.200/ 7306 =

6.756 MiB

( 0.0%)

CALTREND:

45.500/13537 =

3.442 MiB

( 0.0%)

FT1:

39.100/13537 =

2.958 MiB

( 0.0%)

DIGIHIST:

32.600/13537 =

2.466 MiB

( 0.0%)

etc...

 

 

 

...

Cleanup summary

...

If the most aggressive policy discussed so far is enacted, one would liberate space as follows:

Scratch

50 TB

Reprocessing

18 TB

Monte Carlo

29 TB

Total

97 TB

(about 10% of total)

Replacing Existing Disks

This option was received with a frown from CD. Of course, Oracle has thought of this and charges a lot for the replacement drives, which have special brackets. And then there is the manpower to replace and the shell game of moving the data around. We'd have to press a lot harder to get traction on this option.

...