From owner-freebsd-stable@freebsd.org Mon Sep 5 20:14:24 2016 Return-Path: Delivered-To: freebsd-stable@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 08F1DB96E1F for ; Mon, 5 Sep 2016 20:14:24 +0000 (UTC) (envelope-from jim@ohlste.in) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C07EBA14 for ; Mon, 5 Sep 2016 20:14:23 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mail-qk0-x236.google.com with SMTP id l2so199209698qkf.3 for ; Mon, 05 Sep 2016 13:14:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ohlste-in.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=uTXojigi/hkbvdvRn3GJP6w7CtCJbXoZ8TVRE/z5EyQ=; b=vhpOukYm/Q1OcezhRxTZcsmj/pBeV7GbcivAAq3lhJA6XqLZSfbJIwYlEyJlokBgA7 BMrpJA1g3nb4wVK3QPW3NfKKoMOr8QVnmTaywlnjgDVrxg76Lq2VnxNCik8BjsOlH58/ uAmW6uDCbKXmBYpLQtN/87hD5Zql/G1CE/oXjTTbjgQKElTuJRaGWcTIU5VKteF0DLfS 19l7X8QeHcSVR//n46lC/szwK6A3fwx5iacoyxs6q3HihsJKfZM60nnCod8dW8J7Hxs+ so51JkaJ14QjQwqHHzQhL1u8XHSWfOVhLSpAW6UjSD75h5mai5PYy18azcJFIlu2tzlC C7bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=uTXojigi/hkbvdvRn3GJP6w7CtCJbXoZ8TVRE/z5EyQ=; b=QoaKaPBIFhJyPQOmncIth/LzBt4o53FDU2lRkoFp4Imqp6b3orGzf6UCWqP+/+O8ZV 53jIaO/jebDMJE/xcghxrj+Nx4gzrEiRnXDw1RHNyWZiLFrqBy6CUfLmlitGovyIEIzO JYkEYNiOGHn9OGYNvCjq00/B1tEqwDii6LctPe8LDaOTCgnvo8b9W1VxkHuAsAJ0xi2f FhDKsj8Ck9dN7+bZACLyBM0J6ZArcRikOrwdWc+aoNe/CN6pjBPU5lUalX5Aleflwkxr Ek88NXV5JDNAjTPkqH/s35rqJNaFZE9GQX14OkYK78flIBGutKv94MAJhOfNXN1fAJYq FH6Q== X-Gm-Message-State: AE9vXwO56t3Qn/SCLDXz4KhjXR4Wer6r9sDiqBysxlfoj5CItDr2FiEMSWaDc9A/zT1FNQ== X-Received: by 10.55.140.131 with SMTP id o125mr41599093qkd.17.1473106462064; Mon, 05 Sep 2016 13:14:22 -0700 (PDT) Received: from [192.168.1.6] (pool-108-39-64-29.nrflva.fios.verizon.net. [108.39.64.29]) by smtp.gmail.com with ESMTPSA id z52sm5028089qta.40.2016.09.05.13.14.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Sep 2016 13:14:20 -0700 (PDT) To: FreeBSD Stable ML From: Jim Ohlstein Subject: AIO not working on NFS share - ? Regression Message-ID: <6c9093cd-1323-77b1-b27e-f53b58ec86e4@ohlste.in> Date: Mon, 5 Sep 2016 16:14:18 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2016 20:14:24 -0000 Hello, For sometime now we've used a backend (non-internet accessible) server to generate static content that is shared via NFS to a front-end server for internet access. Both machines use ZFS exclusively. The webserver is nginx and we had AIO set to on, with the AIO module built into the kernel.In 10.x it "just worked". About two weeks ago I upgraded that backend machine to 11-STABLE in order to start building packages for 11. I've just updated it again to r305417. I don't recall it not working as expected. More recently I upgraded the front-end machine to 11-STABLE @r305311. Since then, AIO is not working and I get a critical error in the nginx logs like this: 2016/09/05 15:58:02 [crit] 21145#0: *649 aio_read("/path/to/file") failed (45: Operation not supported) while sending response to client ... In 11 AIO is built into the kernel by default, and I have confirmed that it works as expected in files from a local file system. Since the webserver isn't aware that the file system in question is shared via NFS, it seems this is an operating system issue. -- Jim Ohlstein