From owner-freebsd-testing@freebsd.org  Tue Feb 21 03:11:39 2017
Return-Path: <owner-freebsd-testing@freebsd.org>
Delivered-To: freebsd-testing@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 387C9CE7808
 for <freebsd-testing@mailman.ysv.freebsd.org>;
 Tue, 21 Feb 2017 03:11:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
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 27A686CF
 for <freebsd-testing@freebsd.org>; Tue, 21 Feb 2017 03:11:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1L3Bd3W082466
 for <freebsd-testing@freebsd.org>; Tue, 21 Feb 2017 03:11:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-testing@freebsd.org
Subject: [Bug 217261] sys/aio/aio_test:aio_md_test fails semi-frequently with
 Jenkins with "aio_write failed: Operation not supported"
Date: Tue, 21 Feb 2017 03:11:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: tests
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: asomers@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217261-32464-oHz9bbGxfF@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217261-32464@https.bugs.freebsd.org/bugzilla/>
References: <bug-217261-32464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 03:11:39 -0000

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

--- Comment #1 from Alan Somers <asomers@FreeBSD.org> ---
I noticed that problem, but I can't reproduce it locally.  This is what jhb
told me:

Hmmm, qphysio to a character device is always considered "safe".  The
failure must be due to another reason (e.g. there is a system-wide
quota on the number of AIO character device requests in flight).

You might want to see if vfs.aio.num_buf_aio =3D=3D vfs.aio.max_buf_aio when
it fails.

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