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 1soKnm-00AOBZ-N8 for pgsql-general@arkaria.postgresql.org; Wed, 11 Sep 2024 10:42:23 +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 1soKnl-00EgrN-3Q for pgsql-general@arkaria.postgresql.org; Wed, 11 Sep 2024 10:42:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1soKnk-00EgrC-Lw for pgsql-general@lists.postgresql.org; Wed, 11 Sep 2024 10:42:20 +0000 Received: from mail-ej1-x62a.google.com ([2a00:1450:4864:20::62a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1soKne-000cDM-1L for pgsql-general@lists.postgresql.org; Wed, 11 Sep 2024 10:42:19 +0000 Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-a866902708fso51812766b.2 for ; Wed, 11 Sep 2024 03:42:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726051333; x=1726656133; 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=jqHHP6CTP18uePbaKB30UNeQj6lgGXpNPsoo+grDetM=; b=hhQNYDPkzGnrn24vWWTOF27VgiqQfvmXAKnkd6LHqOMcMs1Tct3G6kQp91C1nahQlc ymDbEBzc7XH2Zu5b94me+kkmXyhAH9fy4RWW/btrc3wJFkdLka/YhrqF52+smTxhD2Xk kV+ns9DRWSifvwM7RTCH3FCQzL7zQgUSwYHQeMlNcsnUNkLXG4Yq/0L3J6uAwv2eefuz yUAGqNM7w/ccad4F8G2EVhSL9v9s6GdRNVlfyFJR4ObpF2K+Jo5FgVfksDbYGm95M7jA FcdCrJ/5NGsSfErlrWucI4GDqCdb9ZzOTFz0/GD+hf9LaAWQ6yVQcuqvXudNSGwljAhx +2Qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726051333; x=1726656133; 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=jqHHP6CTP18uePbaKB30UNeQj6lgGXpNPsoo+grDetM=; b=AvsnaXWpWrw15I4nZj+zNuspn40s7KJHklNmRMRs1MqmmGXx80k2qLhlXzkuP8H3F+ uKS5ps8WbEnzj16dcEH/W1M0P5fUGyeW7QXQ5UumLQVInhjhw6guqXK8IUzOegHSEyu/ XVbhaqGq58SRVA6Yt9Z67LqexWTtranNI/ZOg8MIoKu2jTTPtHHMcNxgVzGC47b5+g/R wIeZ9ysWHyuPz6ufXn/KJMW1wO+NcVgskHQ6dAm/3fbbGfvQTnPr+HQayk8wKf7qyiia v8qmGvWpY1hI84bz/hj49tw5wYinQ0kQ5VNoJ5+0YNA5Rdxzgp3Z8Euyvwa1gxsG99H6 tx9A== X-Forwarded-Encrypted: i=1; AJvYcCVOqzxy5goisQ1hJOI3u3PunQOsvzf3oPXPeLA70TaHBvsu4ZpAe8HL/zr4mFF0yZv5Vo/vE6iYtx1g2L/0@lists.postgresql.org X-Gm-Message-State: AOJu0YzVyJ2Lw9UBAhsD/B8Z0jiSb/XrLE54+Nqd6e5IbYPeMu2mjJsh SiwZKTDUjf9FDSsVsYjnV2gQSm7xM2VxahP4MUxJhHSKeMZ/u7xRuf0bIJbuwvGXditKK+1iYCj QDTPw2Q2f55uA1Ay2jC9vSbwszuQ= X-Google-Smtp-Source: AGHT+IFJE/mDdcnpftn+2f//osf8VhAyOgmmDFa2ZcTqkbQk7SL0gxduezAn42vTKCjj1Chi7H92E0aEkmRW66m3Or0= X-Received: by 2002:a17:907:608c:b0:a7a:9447:3e88 with SMTP id a640c23a62f3a-a8ffade0b31mr169295866b.10.1726051332709; Wed, 11 Sep 2024 03:42:12 -0700 (PDT) MIME-Version: 1.0 References: <202409110955.6njbwzm4ocus@alvherre.pgsql> In-Reply-To: <202409110955.6njbwzm4ocus@alvherre.pgsql> From: Thomas Munro Date: Wed, 11 Sep 2024 22:44:52 +1200 Message-ID: Subject: Re: Error:could not extend file " with FileFallocate(): No space left on device To: Alvaro Herrera Cc: =?UTF-8?B?UGVjc8O2ayBKw6Fu?= , "pgsql-general@lists.postgresql.org" , Andres Freund 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 Wed, Sep 11, 2024 at 9:56=E2=80=AFPM Alvaro Herrera wrote: > On 2024-Sep-10, Pecs=C3=B6k J=C3=A1n wrote: > > After upgrade of Posgres from version 13.5 to 16.2 we experience follow= ing error: > > could not extend file "pg_tblspc/16401/PG_16_202307071/17820/3968302971= " with FileFallocate(): No space left on device > > > > We cannot easily replicate problem. It happens at randomly every 1-2 we= eks of intensive query computation. > > Was there some changes in space allocation from Posgres 13.5 to Posgre= s 16.2? > > > > Database has size 91TB and has 27TB more space available. > > Yes, there were some changes in that area. I have a report from > somebody running EPAS 16 which has a problem that looks pretty much the > same as yours -- and the code is essentially identical. I gave them the > attached patch, hoping that it would shed some light ... but so far, > we've been unable to capture any useful intel. What kernel version and file system are these running on (both cases)?