1. 15 Jan, 2021 1 commit
  2. 14 Jan, 2021 1 commit
  3. 15 Nov, 2019 1 commit
  4. 27 Sep, 2017 1 commit
  5. 21 Sep, 2017 1 commit
    • Eric Cano's avatar
      Fixed wait drive ready timeout when mounting. · 43d81927
      Eric Cano authored
      The value was 10 minutes instead of 1. This value was too high as this represents the load time
      of the drive, which is rather fast. Also it was misaligned with the mount to transfer state transition
      timeout, which led to some sessions being killed instead of failing by themselves.
  6. 26 May, 2017 1 commit
  7. 03 Apr, 2017 1 commit
    • Eric Cano's avatar
      cta/CTA#46: Adding garbage collection for object store structures: · cfe8f58b
      Eric Cano authored
      Created a garbage collector subprocess for the drive daemon.
      Created a AgentHeartbeat thread and added it to frontend, drive subprocess and GC subprocess.
      Fixed logs and drive subprocess.
      Renamed common/threading/Threading.[hc]pp to Thread.[hc]pp as there is only one class left in this file.
  8. 08 Nov, 2016 1 commit
  9. 11 Oct, 2016 2 commits
    • Steven Murray's avatar
      Deleted mediachanger dir from castor dir · b38715e6
      Steven Murray authored
    • Victor Kotlyar's avatar
      Ported commits from castor/master for Encryption: · 1a3812e0
      Victor Kotlyar authored
        CASTOR-5350: Introduce encryption SCSI commands in tape drive
        Implementation of two methods:
          * setEncryptionKey(key): Sets encryption params to drive.
          * clearEncryptionKey: Clears encryption params from drive.
        Added support for an interface script that will setup drive
        encryption per tape
        Migrate TapeWriteSingleThread::TapeCleaning::~TapeCleaning() body to
        CASTOR-5350: Refactor support for only external key management script
        Merge branch 'encryption_backend' into 'master'
        CASTOR-5350: Encryption backend
        ## Description
          The aim of this merge request is to incorporate encryption support
          into CASTOR.
          The proposed changes are to be used in conjunction with the
          The **aim** is to enable encryption in specific tape pools of
        ## Changes
          * Introduce encryption SCSI backend to DriveGeneric.
          * Introduce encryption control wrapper
          * (`castor/tape/tapeserver/daemon/EncryptionControl`) for
          * abstracting the two sub-components of:
            * Calling the `ExternalEncryptionKeyScript`,
            * Calling the equivalent DriveGeneric function for
            * passing/clearing the encryption parameters to/from the drive.
          * Add new configuration option in `castor.conf` for the external key
          * management script.
          * Create a Subprocess wrapper for executing external commands as
          * CASTOR children (`castor/server/Subprocess.{h,c}pp`).
          * Incorporate encryption handling in the:
            * DataTransferSession
            * LabelSession
            * CleanerSession
          * Add encryption control timer in the task Watchdog.
        See merge request !1
        Clear encryption key only when encryption enabled
        Changes include:
          - Making EncryptionControl stateful
          - Calling clearEncryptionKey on the drive only when encryption is
        Also includes a minor duplicate code fix on DriveGeneric.
        Merge branch 'encryption_changes' into 'master'
        Clear encryption key only when encryption enabled
        ## Description
          Changes include:
          - Making EncryptionControl stateful
          - Calling `clearEncryptionKey()` on the drive only when encryption
            is on.
          Also includes a minor duplicate code fix on **DriveGeneric.cpp**.
        See merge request !2
        Check if the drive has encryption capability enabled:
          * Add isEncryptionCapEnabled() vendor-specific function
          * Check isEncryptionCapEnabled() before passing encryption params
          * Check isEncryptionCapEnabled() before clearing encryption params
          * Clear encryption key before unencrypted I/O
        Merge branch 'encryption_capability_enabled' into 'master'
        Drive encryption capabilities inclusion
        ## Description
          The aim of this merge request is to address issues related to
          encryption on drive without the encryption capability enabled.
          More specifically:
            * It introduces a vendor-specific way of identifying if the drive
            * has encryption capability enabled
            * **IBM**: Through the SPIN index SCSI page
            * **Oracle**: Through the general INQUIRY SCSI page
            * If the data to be written are to be encrypted, an additional check
            * of the encryption capability of the drive is made. In case of
            * encrypted data, but no encryption capability, the session fails.
            In essence, all encryption related operations are made modulo the
          encryption capability of the drive.
            Last, in case of unencrypted I/O, we clear the keys of the drive (if
          encryption capable) to avoid encrypted data with previous keys on
          CASTOR's system failure.
        ## Testing
          Before the merge request's submission, the following tests were
            On drives with **encryption capability enabled**:
              * Label session
              * Label with previously set encryption key
              * Write without encryption
              * Read without encryption
              * Write with encryption
              * Read with encryption
              * Write with previously set encryption key
              * Read with previously set encryption key
            On drive with **encryption cabability disabled**:
              * Label session
              * Write without encryption
              * Read without encryption
              * Write with encryption - session **should** fail
              * Read with encryption - session **should** fail
          See merge request !3
        Secure session against invalid encryption script output
        Changes in encryption workflow
          - VMGR tag is updated only on write operations
          - Empty key signifies no encryption
        Minor encryption log enhancements
          * Error line in Read/Write session with ErrorMesage key
          * Fix for delimiter in the end of arguments in argsToString()
        Merging in improvements on tape encryption support.
        Removed nullptr which is not supported in SLC6's gcc.
        Added automatic deletion of json objects in
        Fix log typo
  10. 03 Oct, 2016 2 commits
    • Victor Kotlyar's avatar
      Ported commits from castor/master: · 28c7456a
      Victor Kotlyar authored
        Removed redundant setting of the TPVID paramter while mounting the
        tape. This had the nasty side effect of removing the parameter after
        leaving the functions (for all the following logs).
        CASTOR-5323 Tapeserver logs inconsistencies
        Removed duplicate setting of a scoped TPVID parameter in the logs.
        When going out of scope, the parameter
        made TPVID disappear from following logs, which is not desired.
    • Victor Kotlyar's avatar
      Ported commits from castor/master: · 2c2f4a27
      Victor Kotlyar authored
        Add drive's serial number to logs
          ## Description
            Add the drive's serial number, as read by the SCSI Inquiry command
            to the SCSI metrics log lines.
          ## Changes
            * Add the line to the logs
            * Modify session test to check existence of the property in the log
            * line
  11. 30 Sep, 2016 1 commit
    • Victor Kotlyar's avatar
      Ported commits from castor/master for general,drive,volume SCSI statistics: · e8b4ec34
      Victor Kotlyar authored
        CASTOR-5322 RFE: Enhance tapeserverd logs with SCSI tape drive
        Fix for mhtvl scsi log sense exceptions
        CASTOR-5329 Enhance tape statistics
        CASTOR-5332 RFE: Reduce log level to INFO with MHVTL - SCSI Statistics
          could not be acquired from drive
        Move volume SCSI statistics inside the dtor of TapeCleaningMove volume
          SCSI statistics inside the dtor of TapeCleaning
        ## Description
        When first introduced volume SCSI Statistics (at the moment
        IBM-specific), we explicitly put the function after the unmount of the
        tape was done due to an invalid file descriptor error occurring during
        the SCSI query.
        This bug no longer occurs for IBM drives.
        This may be attributed to the update of firmware of the IBM drives
        Apart from the change of the position of the changes, there is no
        alteration in terms of the metrics reported from the drive to the logs.
        ## Testing
        The tests the new code has been through are:
          * Write/Read file on IBM lib0 drive *(older one)*
          * Write/Read file on IBM lib4 drive *(newer one)*
          * Write/Read file on Oracle T10k drive
  12. 15 Sep, 2016 1 commit
  13. 09 Sep, 2016 1 commit
  14. 06 Sep, 2016 1 commit
  15. 05 Sep, 2016 1 commit
  16. 01 Sep, 2016 1 commit
  17. 29 Aug, 2016 1 commit
  18. 14 Aug, 2015 1 commit
  19. 16 Jul, 2015 2 commits
  20. 15 Jul, 2015 2 commits
  21. 21 Jan, 2015 1 commit
  22. 03 Dec, 2014 1 commit
  23. 02 Dec, 2014 2 commits
  24. 27 Nov, 2014 1 commit
  25. 11 Nov, 2014 2 commits
  26. 30 Oct, 2014 1 commit
  27. 15 Oct, 2014 1 commit
  28. 08 Oct, 2014 1 commit
  29. 07 Oct, 2014 1 commit
  30. 06 Oct, 2014 1 commit
  31. 03 Oct, 2014 2 commits
  32. 24 Sep, 2014 1 commit
  33. 08 Sep, 2014 1 commit