irods: iphymv doesn't move file in composite resource tree

  • master
  • 4-2-stable

Bug Report

iRODS Version, OS and Version

iRODS 4.1.12 Ubuntu 12.04

What did you try to do?

Move a file between two composite resource tree leaf resources using iphymv

Expected behavior

File is removed from one resource and added to the other, retaining timestamp, ‘good replica’ status and replica no.

Observed behavior (including steps to reproduce, if applicable)

File is not moved

$ ils -L izonereport.out
  irods-g1-dev      0 root;replicate;red;red2;irods-seq-i13-fg       552918 2016-09-19.11:12 & izonereport.out
    bd646bf8fa97195ce723bab63c880ed1    generic    /irods-seq-i13-fg/home/irods-g1-dev/izonereport.out
  irods-g1-dev      1 root;replicate;green;green4;irods-seq-sr04-ddn-gc10-3-4-5       552918 2016-09-19.11:12 & izonereport.out
    bd646bf8fa97195ce723bab63c880ed1    generic    /irods-seq-sr04-ddn-gc10-3-4-5/home/irods-g1-dev/izonereport.out
$ iphymv -M -S 'root;replicate;red;red2;irods-seq-i13-fg' -R 'root;replicate;red;red1;irods-seq-i07-de' -v /seq-dev/home/irods-g1-dev/izonereport.out
   izonereport.out                 0.000 MB | 0.427 sec | 0 thr |  0.000 MB/s
$ echo $?
0
$ ils -L /seq-dev/home/irods-g1-dev/izonereport.out
  irods-g1-dev      0 root;replicate;red;red2;irods-seq-i13-fg       552918 2016-09-19.11:12 & izonereport.out
    bd646bf8fa97195ce723bab63c880ed1    generic    /irods-seq-i13-fg/home/irods-g1-dev/izonereport.out
  irods-g1-dev      1 root;replicate;green;green4;irods-seq-sr04-ddn-gc10-3-4-5       552918 2016-09-19.11:12 & izonereport.out
    bd646bf8fa97195ce723bab63c880ed1    generic    /irods-seq-sr04-ddn-gc10-3-4-5/home/irods-g1-dev/izonereport.out

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 22 (14 by maintainers)

Commits related to this issue

Most upvoted comments

The DataObjPhymv within a resource hierarchy piece of this is now fixed. The triple replica piece is suspected to have to do with concurrency (at least in 4.2.x) and so will be considered resolved with the introduction of logical locking. This will be closed along with #3848 unless there are objections.