Last modified 5 years ago Last modified on 01/10/17 16:00:46

dCache Tier I meeting January 10, 2017

[part of a series of meetings]

Present, Tigran), PIC(Marc), KIT(Xavier)


(see box on the other side)

Site reports


Everything was OK over Christmas, so no incidences to report.

Problem with enstore

Migration to 2.16 issue with enstore -- email to Dmitry -- cc Sasha --

Function in Chimera called enstoreLevel2Info. Upload new files to dCache -- t_locationinfo fields have a different order.

The error looks like:

[chimera@] 2017-01-02 13:33:58 GMT: QUERY: INSERT INTO t_locationinfo VALUES (NEW.inumber,0,'enstore:',10,NOW(),NOW(),1)

Marc to open a ticket.

UPgrade delayed

Plan to update 17th of January, but

Scheduled update to v6 of enstore.

Plan upgrade to v3 this year.

New instance

PIC supports the VO CIEMAT. Plan to create a federated storage using dCache, similar to NDGF.


Things are running well -- no problems within dCache over last 3 weeks.

SQL function

Tigran to work on this

Migration of tape to HPSS

Internally uses MD5 checksums.

Can dCache support MD5 checksums?

Sort of -- with the limitations that a pool uses a single checksum algorithm and WLCG still uses ADLER32. dCache can store multiple checksums, but there's currently no mechanism to generate multiple checksums.

Support tickets for discussion

[Items are added here automagically]


Proposed: same time, next week.