From owner-freebsd-bugs@FreeBSD.ORG  Thu Dec  4 06:23:47 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 473B3E85
 for <freebsd-bugs@FreeBSD.org>; Thu,  4 Dec 2014 06:23:47 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1576FECE
 for <freebsd-bugs@FreeBSD.org>; Thu,  4 Dec 2014 06:23:47 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB46NkFV007364
 for <freebsd-bugs@FreeBSD.org>; Thu, 4 Dec 2014 06:23:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195349] CAM status: Command timeout since upgrade to 10.1
Date: Thu, 04 Dec 2014 06:23:47 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: olivier@cochard.me
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195349-8-Fy1tjGYiYs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195349-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195349-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 06:23:47 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349

--- Comment #10 from olivier@cochard.me ---
I reach to finish an 12 hours ZFS scrub by disabling MSI interrupts for AHCI !
(thanks mav@ for the temporary workaround).

Here is how to do it:

echo 'hint.ahci.0.msi="0"' >> /boot/loader.conf
shutdown -r now

Once rebooted, check that `vmstat -i` report ahci0 using interrupt below 256.
Like this example:

root@nas:~ # vmstat -i
interrupt                          total       rate
irq17: ehci0 ehci1+                19403          4
irq18: ohci0 ohci1+                    4          0
irq19: ahci0                        3908          0
irq256: hpet0:t0                  112433         26
irq257: hpet0:t1                   33742          8
irq260: bge0                        3354          0
Total                             172844         41

With this workaround, ZFS scrubbing is finished without any "Command timeout":
root@nas:~ # zpool status
  pool: storage
 state: ONLINE
  scan: scrub repaired 0 in 11h55m with 0 errors on Thu Dec  4 01:29:42 2014
config:

        NAME        STATE     READ WRITE CKSUM
        storage     ONLINE       0     0     0
          raidz1-0  ONLINE       0     0     0
            ada0p1  ONLINE       0     0     0
            ada1p1  ONLINE       0     0     0
            ada2p1  ONLINE       0     0     0
            ada3p1  ONLINE       0     0     0
            ada4p1  ONLINE       0     0     0

Can someone test this workaround and report its result too ?

-- 
You are receiving this mail because:
You are the assignee for the bug.