Name and port collision are possible when multiple origins replicate to a single replica

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up server A with a master volume (volume1) which you want to
replicate to server C using port 11325 on C. Port is stored in
/var/lib/zumastor/volumes/volume1/targets/C/port

2. Set up server B with a master volume (volume2) which you want to
replicate to server C using port 11325 on C. Port is stored in
/var/lib/zumastor/volumes/volume2/targets/C/port

3. As the port is not stored in the replica, C cannot tell B not to use
port 11325

What is the expected output? What do you see instead?

Expected to work fine, will probably lead to corruption or to never
replicate (depending on how well TCP behaves).

What version of the product are you using? On what operating system?

Zumastor 0.6, Ubuntu 7.10

Please provide any additional information below.

I think the same might happen with volume names.

Original issue reported on code.google.com by pgqui...@gmail.com on 12 Feb 2008 at 7:35

[GoogleCodeExporter]

Probably this issue can be interpreted as a generalization of issue 65

Original comment by pgqui...@gmail.com on 13 Feb 2008 at 1:35

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Issue 65 was fixed, so I believe this is fixed too.

Original comment by williama...@gmail.com on 5 May 2008 at 4:45

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****