Page History
...
- Intend to use xrootd for storing data files (mainly *.root, *.fits)
- MC simulations, test data and real data from satellite
- Want xrootd to manage many physical disks
- Want xrootd to manage archiving of files to HPSS (with recovery from tape expected to be rare)
- All files to be put into xrootd should also be registered in data catalog
- Files are first put into xrootd, then registered in data catalog
- This is not an atomic transaction
- Data catalog has "crawler" which verifies existence of files after they have been added
- Extracts checksum, creation date, # events etc
- If file exists in multiple locations (e.g. xrootd and NFS) checks consistency of files.
- Files are first put into xrootd, then registered in data catalog
Issues (mainly based on Tom's input)
...
- unreliability of redirector-server link for writing files. If a server containing an old version of a file is delayed, off the network, hung or shutdown, the redirector writes the new file to a new server. This results in a situation with two copies of different versions of the same file.
- The xrootd servers (redirector and disk servers) have in the past failed to restart after machine reboot (or failed to start talking to each other after reboot), this should needs to be fixed.
- There is a known bug in the xrootd "rm" command which can result in client code hang.
- The "xrdcp -f" command is not working
- The "rm" command now only removes an xrootd file from disk - and not HPSS. This is probably okay unless a new version of that file is created, which may cause confusion.
- This may become more critical when we add the ability to automatically tar files before archiving them
...
Overview
Content Tools