Uploaded image for project: 'onedata'
  1. onedata
  2. VFS-11721

Investigate eperm on archive creation

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • 21.02.5
    • None
    • None
    • None
    • Sprint 254, Sprint 255: Ribald Rename, Sprint 256: Stinky Storage, Sprint 257: Tedious Ticket, Sprint 258: Ultimate Unrespons, Sprint 259: Vicious Version
    • 4

      {{nocatch,eperm},[{data_access_control,assert_access_permitted_by_protection_flags,2,[

      {file,"/build/op-worker-Jbm04o/op-worker-21.02.3/src/modules/fslogic/security/data_access_control.erl"}

      ,

      {line,174}

      ]},{storage_driver,open_with_permissions_check,3,[

      {file,"/build/op-worker-Jbm04o/op-worker-21.02.3/src/modules/storage/driver/storage_driver.erl"}

      ,

      {line,682}

      ]},{replica_dbsync_hook,'maybe_truncate_file_on_storage/3-fun-0',3,[

      {file,"/build/op-worker-Jbm04o/op-worker-21.02.3/src/modules/fslogic/replication/replica_dbsync_hook.erl"}

      ,

      {line,411}

      ]}]}

      this happens on first archive creation in newly supported space by at least 2 providers on provider not doing archivisation

            plgmstanisz Michał Stanisz
            plgmstanisz Michał Stanisz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: