User Tools

Site Tools


cluster:eos

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cluster:eos [2019/02/13 15:30] bernetcluster:eos [2022/01/20 10:40] (current) bernet
Line 6: Line 6:
  
 ==== EOS ==== ==== EOS ====
-EOS is an open-source storage software solution to manage multi PB storage for the CERN Large Hadron Collidor LHC. Core of the implementation is the XRootD framework providing a feature-rich remote access protocol.+EOS is software solution that aims to provide fast and reliable multi-PB disk-only storage technology for both LHC and non-LHC use-cases at CERNThe core of the implementation is the XRootD framework which provides feature-rich remote access protocol. The storage system is running on commodity hardware with disks in JBOD configuration. It is written mostly in C/C++, with some of the extra modules in Python. Files can be accessed via native XRootD protocol, a POSIX-like FUSE client or HTTP(S) & WebDav protocol.
  
 ==== EOS Command ==== ==== EOS Command ====
Line 24: Line 24:
  
 ==== EOS Fuse Mount ==== ==== EOS Fuse Mount ====
-On our cluster some of the EOS instances are mounted with fuse, so they look like normal file systems to you and you can use standard linux commands. The mounted file systems are:+On our cluster all of the EOS instances are also mounted with fuse, so they look like normal file systems to you and you can use standard linux commands. There is no need to use the ''eos'' commands anymore. The mounted file systems are:
   * eoscms --> ''/eos/cms/''   * eoscms --> ''/eos/cms/''
   * eoslhcb --> ''/eos/lhcb/''   * eoslhcb --> ''/eos/lhcb/''
   * eosuser --> ''/eos/user/''   * eosuser --> ''/eos/user/''
 +  * ...
 To access these file systems, you need to have a CERN Kerberos ticket as for the EOS commands, but in addition you need to pass the ticket to the fuse system with the command ''eosfusebind'', similar to the ''aklog'' command for AFS. You need therefore to execute the following commands:\\ ''kinit <cern_username>@CERN.CH ; eosfusebind'' To access these file systems, you need to have a CERN Kerberos ticket as for the EOS commands, but in addition you need to pass the ticket to the fuse system with the command ''eosfusebind'', similar to the ''aklog'' command for AFS. You need therefore to execute the following commands:\\ ''kinit <cern_username>@CERN.CH ; eosfusebind''
  
Line 33: Line 34:
 EOS commands and Linux commands in the EOS file system are not very resource efficient. If you need to transfer large amount of data, use the ''xrdcp'' command: EOS commands and Linux commands in the EOS file system are not very resource efficient. If you need to transfer large amount of data, use the ''xrdcp'' command:
   * ''<nowiki>xrdcp root://eoslhcb.cern.ch//eos/lhcb/user/b/bla/eos_tutorial/eos.txt eos.txt</nowiki>''   * ''<nowiki>xrdcp root://eoslhcb.cern.ch//eos/lhcb/user/b/bla/eos_tutorial/eos.txt eos.txt</nowiki>''
-  * ''<nowiki>xrdcp eos.txt root://eoslhcb.cern.ch//eos/lhcb/user/b/bla/eos_tutorial/eos.txteos.txt</nowiki>''+  * ''<nowiki>xrdcp eos.txt root://eoslhcb.cern.ch//eos/lhcb/user/b/bla/eos_tutorial/eos.txt eos.txt</nowiki>''
  
cluster/eos.1550068215.txt.gz · Last modified: 2019/02/13 15:30 by bernet