[DragonFlyBSD - Bug #2610] Hammer mirror copy causes extreme slowdown on new ssh connections

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Fri Mar 14 11:14:44 PDT 2014

Issue #2610 has been updated by t_dfbsd.

Just an update that this is still an issue on v3.7.1.800.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 and the SSH session I was in hung for over a minute. It eventually returned. While it was hung, I tried to open a new SSH session to the machine and that took over a minute to connect.

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 normal.

dmesg.txt (17.8 KB)

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: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list