Date: Wed, 24 Jan 2018 04:51:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 225337] z_teardown_inactive_lock held inordinately long Message-ID: <bug-225337-3630-dPDOR5revu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225337-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-225337-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225337 --- Comment #4 from Garrett Wollman <wollman@FreeBSD.org> --- I changed the schedule of the replication cron job (which runs every 15 minutes) to *not* run during the usual backup window (which I don't have any control over but is fairly consistent) and thus far have not seen the hang,= so I think I can reasonably conclude that the combination of "zfs recv -F" and active backup traversal (or any other heavy use of the filesystem?) is toxi= c. The filesystems in question are a special case for us, because the active w= rite site is on another group's server; we're doing the replication for backup/DR purposes. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225337-3630-dPDOR5revu>