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 copy a large file, or large set of 
files, from one disk to the other?  The problem happens a while after the 
hammer copy starts, so it's probably fine while the system figures out what to 
move in what parts, and then starts to slow down when the actual data transfer 
happens.  If it's the data transit itself that causes the problem, a normal 
bulk copy from disk to disk should show the same symptoms.

Your SATA drives in your dmesg are coming up as daX devices - something that I 
thought would only happen with SCSI.  Maybe I don't know what I'm talking 
about, though.

Bug #2610: Hammer mirror copy causes extreme slowdown on new ssh connections

* Author: t_dfbsd
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
I ssh into the machine to do a mirror copy or mirror stream from a master PFS 
on a SATA drive to a newly created slave PFS on a different SATA drive (both 
drives are encrypted).  During the mirror copy everything seems fine and the 
SSH session I'm in seems responsive enough.   CPU usage as reported by top 
doesn't exceed 40%.

If I try to make a new SSH session right after the mirror copy starts it works 
normally.  However, a few minutes after the mirror copy starts, any attempt to 
SSH takes a vey long time to connect.  It appears that other types of network 
connections, like SMB are similarly affected.  There is no activity on the box 
other than the mirror copy or stream.  If I kill that, then things return to 

You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here:

Reply via email to