Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Feb 2016 12:47:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 203864] ZFS deadlock between zfs send, zfs rename and ctrl-C
Message-ID:  <bug-203864-3630-qPMnd6qlvR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203864-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-203864-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=3D203864

--- Comment #6 from roel@qsp.nl ---
We've run into this exact same issue using the zrep script. It's easily
reproducable. The deadlock occurs when a "zfs rename" is executed while the=
re
is still a "zfs send" process running.

In zrep, this occurs when a zfs receive on the remote hosts fails and zrep
immediately attempts to rename a snapshot. However, the zfs send process is
still running (cleaning up?) and this causes an immediate deadlock.

Any zfs process run after that immediately blocks in state
"zpa_namespace_lock". IO continues to work, but fails at some point in the
future. I've not diagnosed the exact trigger that causes IO to seize.

The only resolution is to power cycle the system.

I've just attached the output to a procstat -kk -a from yesterday when I ran
into this.

Running on 10.3-PRERELEASE FreeBSD 10.3-PRERELEASE #1 r294572

--=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-203864-3630-qPMnd6qlvR>