Hi Guenter,

You'll probably want to put metadata (where cinfo files are stored) and root-fs (basically sym-links into data disks) on a non-data disk.

After data disk failure, you replace the disk (or comment it out in the xrootd.cfg) and restart. XRootd will refuse to start if a configured target directory for oss.space does not exist. If you lose disk with meta-data, you have to clear the cache.

You can remove the stale links after data disk replacement but actually don't have to ... each lfn will get cleared when its time comes (when it would be purged or when an open is attempted). Thinking about this, I could add full data-space scan during the startup purge -- normally purge only scans meta-data file to determine "age" of a file.

Cheers,
Matevz

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/975?email_source=notifications\u0026email_token=AA7NRDXV24OFNHIWV5X2FCTP7W4DBA5CNFSM4HLGWH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AVFVI#issuecomment-511791829", "url": "https://github.com/xrootd/xrootd/issues/975?email_source=notifications\u0026email_token=AA7NRDXV24OFNHIWV5X2FCTP7W4DBA5CNFSM4HLGWH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AVFVI#issuecomment-511791829", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1