Troubleshooting remote replication, Truncating a file during replication – HP StoreAll Storage User Manual
Page 195

–
t
means the modification time is different and is being updated to the sender’s value
(requires --times). An alternate value of T means that the time will be set to the transfer
time (without --times).
–
p
means the permissions are different and are being updated to the sender’s value
(requires --permissions).
–
o
means the owner is different and is being updated to the sender’s value (requires
--owner and super-user privileges).
–
g
means the group is different and is being updated to the sender’s value (requires
--group and the authority to set the group).
–
u
means the atime is different and is being updated to the sender’s value.
–
a
means the CIFS ACL is different and is being updated to the sender’s value.
–
x
means the POSIX extended attributes are different and are being updated to the
sender’s values.
◦
Another possible output for %i is - when deleting the files, the "%i" represents the string
"*deleting" for each item that is being removed.
Sample Output of the ibrcfrworker log
(2012/11/19 15:50:40),
nl
(2012/11/19 15:50:40),
nl
(2012/11/19 15:50:40), nl (2012/11/19 15:50:40), nl (2012/11/19 15:50:40), nl (2012/11/19 15:50:40), nl (2012/11/19 15:50:40), Troubleshooting remote replication Continuous remote replication fails when a private network is used Continuous remote replication will fail if the configured cluster interface and the corresponding Truncating a file during replication If a file is truncated while it is being replicated, the file is replicated successfully, but a Domain rsync: read errors mapping "/mnt/ibrix/filter/tasks/5/ifs1/test.dat": No data available (61) rsync: read errors mapping "/ifs1/test.dat": No data available (61) You can ignore these error messages. The file was replicated successfully. Troubleshooting remote replication 195
cluster Virtual Interface (VIF) for the Fusion Manager are in a private network on either the source
or target cluster. By default, continuous remote replication uses the cluster interface and the Cluster
VIF (the ibrixinit -C and -v options, respectively) for communication between the source
cluster and the target cluster. To work around potential continuous remote replication communication
errors, it is important that the ibrixinit -C and -v arguments correspond to a public interface
and a public cluster VIF, respectively. If necessary, the ibrix_crr_nic command can be used
to change the server assignments (the server/NICs pairs that handle remote replication requests).
scan failure message is displayed. Also, an error message is logged in the ibrcfrworker.log
file. The text of the message is similar to the following: