Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZ5Y-0004ny-Lg for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Feb 2019 02:55:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gvZ5X-0007gA-DQ for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Feb 2019 02:55:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZ5W-0007fN-Fh for pgsql-bugs@lists.postgresql.org; Mon, 18 Feb 2019 02:55:23 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZ5S-0000Zw-56 for pgsql-bugs@lists.postgresql.org; Mon, 18 Feb 2019 02:55:21 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C488221BC4; Sun, 17 Feb 2019 21:55:16 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 17 Feb 2019 21:55:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=SZ/puJ/JfihBdoHxpclYwhcjYCn vOwEt/bM7OaKnY2g=; b=ZaI3qHmbl7wRiqwxLrH23i105GJ5t/hCeD8s0GtargQ JKTc85cxMy6nEE4w9DewN3HDTubBLL2c7qV3HpCE5vHIGBvpGX7FnyGb2gtjeSpf uVyv5SgTwEM40e0WDzB0qDe7/yGcBzsDOLp5xMPjEvcsxqNx37XSySXtlEYsUtD0 8ac0ZRd+vL5m/0nOWMKB+t86wkyFkxtQ2+bNOQ2rbX4f9hxHq5OqScYP3zR9zmZv zwYysxO1oMBqulcTegFG/v/mRpgbKrYlrJsfBEpQk0ScxdFzCcT0pS3SG7QT96rO W4/80c0urLGQqovNT3R1S9Dt0rZVAUITEXCiDSWeKlA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=SZ/puJ /JfihBdoHxpclYwhcjYCnvOwEt/bM7OaKnY2g=; b=1VZkrWECd/3V+A/gXrGEDG 2P8l4fQLxQMzD5yvJZY8uRbWSUrO6k6yckwEbMnv4RCm+d0IabyJXgzOzNl3PY6B ImAKsDs+dBxfgxWzAua7u4LhVQWi8fpJPr47liks60cGjJ09QLhOwQHQsthLvJvu RvyhaSunOq7TK6uiZtHXhHaqG/87LotGz6qaNo+KV1GvJBgIywCkzYx8vjWsRDdN QAF8iKQuKbB0U2/yaje1H26AQ+se5YmIfl6Y8rjEspgb1v+Yw/EXvAm6XAC8GAsF gCcxkuZjdFsTTuC4D/8OOEczTxyofTkfZtUxbSxvatSrUQpmHw/O/dDYGt8wlmcQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrudduvddgheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtd dmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgt hhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqne cukfhppeduudekrddvgedurddvgeelrdduudelnecurfgrrhgrmhepmhgrihhlfhhrohhm pehmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (mp76f1f977.ap.nuro.jp [118.241.249.119]) by mail.messagingengine.com (Postfix) with ESMTPA id B3E10E423B; Sun, 17 Feb 2019 21:55:14 -0500 (EST) Date: Mon, 18 Feb 2019 11:55:11 +0900 From: Michael Paquier To: Thomas Munro Cc: John Klann , PostgreSQL mailing lists Subject: Re: BUG #15636: PostgreSQL 11.1 pg_basebackup backup to a CIFS destination throws fsync error at end of backup Message-ID: <20190218025511.GA15532@paquier.xyz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 18, 2019 at 02:34:15PM +1300, Thomas Munro wrote: > You mentioned that you were on RHEL 7.5, which ships with a 3.10 > kernel. When you eventually move to RHEL 8 (4.x) or even install an > alternative newer kernel for 7.x, the problem will hopefully go away > by itself. Considering that, the lack of other complaints, and the > availability of a workaround (--no-sync followed by "sync"), I'm not > so sure it's worth committing this. If we get to ignore EINVAL, then we won't know that fsync has failed even in cases where the caller has done an incorrect thing by using a special file, which sounds like a bad idea for the core code as much as any plugins calling that? -- Michael --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlxqHo8ACgkQnvQgOdby QH0TmA//QE/2DmZkgrCI+GfQAXye74g2fhVkzxdzwqWRMg6XtWe2XSvIQbY4fNa8 gHIfv6BVkEUTI4/mxGJdMl5myCcBMqUq09NS5lDJoTnSra8JvwQLhL2OnanB0O0i MCBh4k4zz+6N89FDlbNYwjaMkHfGGMOqaSZT2xSyQCcguWL6Yb0OBldNBpbMf+vE 11msBO4xzMpSH6mxbWLeCpteBMs8hOpFb1oVhweN5rcvjYRQRlbJg3h7AAeQ49mV 7wpYneOyGwbS74FAQ/h5vIpp1xvAx3NmMbWnOmCFJVCNJBHL7x+uGMKKmXhYX8iQ oA1KtOFiGr4QjxlNHJMC2RxR3U0t6XsOkqO4gT4lCofnuCgBIZW2c6b1YYpseGJN nE0GfYfO4+6YDXJZxP0rvyQeeNERCEaieN2gwepfeL+XC4nsDi2hwX+LOe4G5jtV GnTpIaMfY0UGXv/W0XR10PBdYF4KkzQkcfxPu9XtyYnd/h1HTqiUupe3zG+tF8KR VZgjeYHeWgHCT/Zjen0JV0L8H+0/uO7IZPII0+HqNJ/6kCbN1+uNi4jowNVhbTI/ EjZCoUeZM3ylXwB9Pl4+nXQu/qK3lhCVtFerUYmQVGeLgdbisaaTvGa/mdXWsjz3 0riTyLkzB+XylJS8O+rEt0E7C51Yj2lw7j8bVWSZjcSuerzyCDc= =BGTM -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--