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 1iaS42-0002D2-K9 for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Nov 2019 22:15:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iaS3z-0003Uc-Al for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Nov 2019 22:15:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaS3y-0003UT-UH for pgsql-hackers@lists.postgresql.org; Thu, 28 Nov 2019 22:15:03 +0000 Received: from mail-yb1-xb43.google.com ([2607:f8b0:4864:20::b43]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaS3r-0004s3-Ew for pgsql-hackers@postgresql.org; Thu, 28 Nov 2019 22:15:02 +0000 Received: by mail-yb1-xb43.google.com with SMTP id v2so10925132ybo.3 for ; Thu, 28 Nov 2019 14:14:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hAEKeD25WiRTqpwVQC9pWIe8q3UueKlAkYXNWVRHPdc=; b=AUxlCvjKGQ2pyUlI1bFWht5DDKXo0BKp2sFBbtHa9uswiHlw90TeBtYPdTTFBIe3nd bt9ZHcaQNiIrJS9nsmAZlxsLSmKol5HU2wtt+cvAp53csUCLHHEvVwaxb/qPfDVXzEkB AQzsn5+5dwzcNsHRQEelG4RzudFdXQuK3ftALdoxJ3WX/pwAJTeJJ5RidbtwCJ1cTzOr l6aLMGzfGNLZIYs11Z37MLhi1NLo+QVF+lfRN7tWNQaOICjNu17RzYBvuaIEwXowFEmn oVVm71HZ4a4DocU7U7BFgio1ZfybcWpakONgPh6PYlW8aLun0Q5oZGTxeLKWZA+sBbdE zK1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hAEKeD25WiRTqpwVQC9pWIe8q3UueKlAkYXNWVRHPdc=; b=WhdOzHmf+XiRgMnlOC825P6RE1BpkrzGxbCe8QZezvDQ4Al2/4NrNHRlpPaYCA/zbQ w+6vxMIj6y69cWzaM931HWxHuC+0CQ/X+X19mJnj7ennIS2ZukwlczNjVHETWsT+4U0r HQl6DBuoKS05TRKS296rWgkAUZN0QZ4bCdl49yxNNXcF8bo6psk7KGjGoyt1/S/z9Uwa Cb4t00pXkbj2JkZZ6fPRwcR6F96cxFJncdOtQMOIpUtpGrE74y8bYznCXBcOF2Td0STe MjZ31FyWO7zXNzTtpxjHWJxGn1a89cJ2bRJcz5tQ7vrnuYhfnIeMhPcxBwG1hpO/frQw 5mGQ== X-Gm-Message-State: APjAAAXfLfScDwV8/uHaekYVjF9oSrzvmwRZem6cT6olFm81C+paKgRm QANxWkY7TNQnlp5sV6+arhcfQg== X-Google-Smtp-Source: APXvYqx9NU+1wEAOzYaG0KVQQKyjro6kacDOjp/tucy1eHePaWCIzYJSRu20h4ly9vMqf07sAJIowA== X-Received: by 2002:a25:c0d6:: with SMTP id c205mr37624995ybf.342.1574979292422; Thu, 28 Nov 2019 14:14:52 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id m16sm4105983ywa.90.2019.11.28.14.14.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Nov 2019 14:14:51 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 4599D800CBC; Thu, 28 Nov 2019 16:14:50 -0600 (CST) Date: Thu, 28 Nov 2019 16:14:50 -0600 From: Justin Pryzby To: Thomas Munro Cc: pgsql-hackers Subject: Re: checkpointer: PANIC: could not fsync file: No such file or directory Message-ID: <20191128221450.GE16647@telsasoft.com> References: <20191119115759.GI30362@telsasoft.com> <20191119224910.GU30362@telsasoft.com> <20191120012226.GW30362@telsasoft.com> <20191121010703.GF30362@telsasoft.com> <20191125212436.GA20096@telsasoft.com> <20191127065313.GU16647@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Nov 29, 2019 at 10:50:36AM +1300, Thomas Munro wrote: > On Fri, Nov 29, 2019 at 3:13 AM Thomas Munro wrote: > > On Wed, Nov 27, 2019 at 7:53 PM Justin Pryzby wrote: > > > 2019-11-26 23:41:50.009-05 | could not fsync file "pg_tblspc/16401/PG_12_201909212/16460/973123799.10": No such file or directory > > > > I managed to reproduce this (see below). I think I know what the > > Here is a patch that fixes the problem by sending all the > SYNC_FORGET_REQUEST messages up front. I managed to reproduce it too, but my recipe is crummy enough that I'm not even going to send it.. I confirmed that patch also seems to work for my worse recipe. Thanks, Justin