Issue #2610 has been updated by t_dfbsd. Just an update that this is still an issue on v184.108.40.2060.g060fb-DEVELOPMENT. I was mirror copying a 4TB PFS from one SATA drive to another in the same machine. After running approximately 12 hours, I ran the command hammer config on a different volume
Issue #2610 has been updated by t_dfbsd. In case I wasn't completely clear, the issue is the time it takes to make the connection for a new ssh session. I timed one and it took over 5 minutes to get me to the shell prompt. Once I'm logged in, the new ssh connection responds normally.
Issue #2610 has been updated by justin. Hmm. I'm doing the exact same thing here on 3.4 (master - slave, both drives in same machine) and not seeing the problem. I haven't modified anything from 'normal'. I don't have as many disks as you, though. If you have the space for it - can you
Issue #2610 has been updated by justin. Does it change anything if you limit the bandwidth used? ( -b 512k or similar) A smaller splitsize? Those are semi-random guesses on my part. Bug #2610: Hammer mirror copy causes extreme slowdown on new ssh
Issue #2610 has been updated by t_dfbsd. I should have said that the mirroring is occurring between two drives on the same machine, so it doesn't sound like the -b option would apply. Does the setting of splitsize only affect the initialization phase of the mirroring? The problem I'm