Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Oct 2015 07:12:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 203864] ZFS deadlock between zfs send, zfs rename and ctrl-C
Message-ID:  <bug-203864-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203864

            Bug ID: 203864
           Summary: ZFS deadlock between zfs send, zfs rename and ctrl-C
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: peter@FreeBSD.org

I tried to abort a zfs send:

07:06:26   2.28G   zroot/j/jails/admin-svn@daily.31
07:06:27   2.29G   zroot/j/jails/admin-svn@daily.31
^C
load: 1.27  cmd: zfs 72318 [tx->tx_sync_done_cv] 101.46r 0.00u 1.89s 0% 4212k
load: 0.84  cmd: zfs 72318 [tx->tx_sync_done_cv] 127.51r 0.00u 1.89s 0% 4212k
load: 0.84  cmd: zfs 72318 [tx->tx_sync_done_cv] 127.98r 0.00u 1.89s 0% 4212k

It turns out the freebsd-snapshot cron was running at that very instant and it
lead to a deadlock:

# ps -axl | grep tx
  0 74866 72290   0  20  0  40336   3528 tx->tx_s D     -     0:00.00 zfs
rename zroot/j/jails/monitor@hourly.15 zroot/j/jails/monitor@hourly.16
  0 72318 69290   0  20  0  42520   4228 tx->tx_s DE+   0     0:01.89 zfs send
-Rv zroot/j/jails/admin-svn@sync.00

I've seen this before but never quite at such a bad time.  Neither can be kill
-9'ed.

-- 
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-8>