Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgboB-0002OA-5d for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jul 2018 20:15:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgbo9-0001u9-00 for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jul 2018 20:15:20 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgbo8-0001u0-Pj for pgsql-hackers@lists.postgresql.org; Fri, 20 Jul 2018 20:15:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgbo5-0006ff-ST for pgsql-hackers@lists.postgresql.org; Fri, 20 Jul 2018 20:15:20 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w6KKFEgH012260 for ; Fri, 20 Jul 2018 16:15:14 -0400 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12258.1532117714.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Jul 2018 16:15:14 -0400 Message-ID: <12259.1532117714@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk We've seen several occurrences of $subject in the buildfarm in the past month or so. Scraping the logs, I find coypu | 2018-06-14 21:17:49 | HEAD | Check | 2018-06-14 23:31= :44.505 CEST [5b22deb8.30e1:124] ERROR: could not read block 3 in file "b= ase/16384/2662": read only 0 of 8192 bytes coypu | 2018-06-14 21:17:49 | HEAD | Check | 2018-06-14 23:31= :44.653 CEST [5b22deb8.6d4d:132] ERROR: could not read block 3 in file "b= ase/16384/2662": read only 0 of 8192 bytes gull | 2018-06-21 04:02:11 | HEAD | Check | 2018-06-20 21:27= :06.843 PDT [31138:3] FATAL: could not read block 3 in file "base/16384/2= 662": read only 0 of 8192 bytes mandrill | 2018-06-22 16:14:16 | HEAD | Check | 2018-06-22 16:46= :24.138 UTC [14353240:43] pg_regress/create_table_like ERROR: could not r= ead block 3 in file "base/16384/2662": read only 0 of 8192 bytes mandrill | 2018-06-22 16:14:16 | HEAD | Check | 2018-06-22 16:46= :24.137 UTC [20710034:1] ERROR: could not read block 3 in file "base/1638= 4/2662": read only 0 of 8192 bytes lapwing | 2018-07-05 07:20:02 | HEAD | Check | 2018-07-05 07:21= :45.585 UTC [24022:1] ERROR: could not read block 3 in file "base/16384/2= 662": read only 0 of 8192 bytes lapwing | 2018-07-05 07:20:02 | HEAD | Check | 2018-07-05 07:21= :45.591 UTC [23941:39] pg_regress/roleattributes ERROR: could not read bl= ock 3 in file "base/16384/2662": read only 0 of 8192 bytes mantid | 2018-07-17 01:20:04 | REL_11_STABLE | Check | 2018-07-16 21:21= :32.557 EDT [26072:1] ERROR: could not read block 3 in file "base/16384/2= 662": read only 0 of 8192 bytes mantid | 2018-07-17 01:20:04 | REL_11_STABLE | Check | 2018-07-16 21:21= :32.557 EDT [25990:82] ERROR: could not read block 3 in file "base/16384/= 2662": read only 0 of 8192 bytes coypu | 2018-07-17 01:27:39 | HEAD | Check | 2018-07-17 03:47= :26.264 CEST [5b4d4aa4.3ac4:71] ERROR: could not read block 3 in file "ba= se/16384/2662": read only 0 of 8192 bytes coypu | 2018-07-20 11:18:02 | HEAD | Check | 2018-07-20 13:32= :14.104 CEST [5b51c833.4884:131] ERROR: could not read block 3 in file "b= ase/16384/2662": read only 0 of 8192 bytes While I didn't go back indefinitely far, there are no other occurrences of "could not read block" failures in the last three months. This suggests strongly that we broke something in early June. Don't know what though. Ideas? In case anyone's wondering, 2662 is pg_class_oid_index. regards, tom lane