Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rq2sC-00AFMT-Og for pgsql-general@arkaria.postgresql.org; Fri, 29 Mar 2024 03:25:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rq2sB-009gBm-E6 for pgsql-general@arkaria.postgresql.org; Fri, 29 Mar 2024 03:25:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rq2sB-009g9H-3A for pgsql-general@lists.postgresql.org; Fri, 29 Mar 2024 03:25:43 +0000 Received: from mail-ej1-x62a.google.com ([2a00:1450:4864:20::62a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rq2s8-007ANt-4f for pgsql-general@lists.postgresql.org; Fri, 29 Mar 2024 03:25:42 +0000 Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-a470d7f77eeso207845166b.3 for ; Thu, 28 Mar 2024 20:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711682739; x=1712287539; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lzuK4A3VI0V9qOu0X9mKFIrfMzMFIa8QdEIYPMno7+M=; b=ljq2O+BFsIjBV3NNh0xJr1Hu1cCyTlA5bl30gsEvmJfJJEaOucUXIWTpwTxEJXmVdE JeSZ/vO9GquKowvzh2KeyRiddfGeRRl7ICx1REgeTRErPO6ptdGIDqRckas2J00LyHeZ 1jQNFjSI+OPFWSPCHSAd4wGCQXelth3mIZPjEoBZJyUaQnwUYut02JoskvBY8ubL8HmA GgZ8BGJhNH+jyyZewLpUCmj+rEHQBJUT4Z7ICvUiRGszjvqGRiLWYEQC5sTne9bfJgui ojj312YaBqOZONRXgsSyOd55Suxi6pd4rt2xzVHYz/ba6Dc/SkB2F9CAPQ07Z4JzA9QD 6UfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711682739; x=1712287539; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lzuK4A3VI0V9qOu0X9mKFIrfMzMFIa8QdEIYPMno7+M=; b=RXvAdvGT5IJeEktTLfl76rGPfTm6o845h/X2mhknIRWcZkvz1756rAe2vLzUUgK0Wo zjHx5WTN+M8mZLnB7VsimUizCLmQeFuEY9zhMwO85ZTNavPgpxs0CCK/yBWJQtblPF5b XfQ2Cm1dAzQlcvMaDv9qC1KRJpbEAK4ngFtIgoPMPKS1dlTSWbsc3V559gVzlw3pxKOd SLrSlQ6je6+sggzjCHYrlmoQqw4wL3+aHeIILNQaBRZDwly/n6Tgd+PhB8DR+uWm3+lQ jZfsrkAZFkq9JJSdcgQ+Q1VhN3Flwv9stSYnNJ0NhA1X1GgTYWeoU3ndhEVDnVqFWzL4 a2kQ== X-Gm-Message-State: AOJu0Yy+uGYdOD5EsMgql6NAAcEFlp3ifagmaQ0o3MaqUkFNjpjrHzcO dKBzo9tjZmepY9GWK6oPNr96LL4AgM0QaGnDphBn7evl3ocw+MO0LlseZFaRadFCBLhNq3JyaeI awVvbf6WymI6CDyEIYvpaEDeIln3sO1vspVhKlg== X-Google-Smtp-Source: AGHT+IFB6FRiW4yILr274ejrEhBLkLKMj0TlU1xMAtPFcNy/o6C343Zcl977ytRHG6PnWgnq3XGcNkFkZfNYw89bpKU= X-Received: by 2002:a17:906:4698:b0:a4e:dff:23c4 with SMTP id a24-20020a170906469800b00a4e0dff23c4mr747830ejr.47.1711682739129; Thu, 28 Mar 2024 20:25:39 -0700 (PDT) MIME-Version: 1.0 References: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com> <2E2F11F8-718A-4E6A-81E0-4F5CC1F1273A@arcict.com> <19556056-40E7-4FA3-A2A1-0A345AEBFD9E@arcict.com> <76FAACAC-F64A-43DA-BDBF-340A40C47045@arcict.com> In-Reply-To: From: Thomas Munro Date: Fri, 29 Mar 2024 16:25:01 +1300 Message-ID: Subject: Re: could not open file "global/pg_filenode.map": Operation not permitted To: Nick Renders Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Mar 29, 2024 at 4:47=E2=80=AFAM Nick Renders = wrote: > Looking at the 2 machines that are having this issue (and the others that= don't), I think it is somehow related to the following setup: > - macOS Sonoma (14.4 and 14.4.1) > - data directory on an external drive > > That external drive (a Promise RAID system in one case, a simple SSD in t= he other) has the option "ignore ownership" on by default. I have tried dis= abling that, and updating the data directory to have owner + read/write acc= ess for the postgres user. It seemed to work at first, but just now the iss= ue re-appeared again. > > Any other suggestions? I don't have any specific ideas and I have no idea what "ignore ownership" means ... what kind of filesystem is running on it? For the simple SSD, is it directly connected, running a normal Apple APFS filesystem, or something more complicated? I wonder if this could be related to the change in 16 which started to rename that file: https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommitdiff;h=3Dd8= cd0c6c95c0120168df93aae095df4e0682a08a Did you ever run 15 or earlier on that system?