From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id EC63A697A5 for ; Mon, 31 Aug 2020 15:11:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D8FA7144A2 for ; Mon, 31 Aug 2020 15:11:08 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 4F9C81448C for ; Mon, 31 Aug 2020 15:11:04 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 0D5CB44964 for ; Mon, 31 Aug 2020 15:11:04 +0200 (CEST) Date: Mon, 31 Aug 2020 15:10:57 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox Backup Server development discussion References: <82142373-8994-8d65-5cc8-6944873bb33e@itronic.at> <1598873753.xg9lm3vlx4.astroid@nora.none> In-Reply-To: MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1598879286.etmszx6yka.astroid@nora.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] Some problems with fullstorage and cleanup X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2020 13:11:39 -0000 On August 31, 2020 2:32 pm, Harald Leithner wrote: >=20 >=20 > On 2020-08-31 13:39, Fabian Gr=C3=BCnbichler wrote: >> On August 31, 2020 1:14 pm, Harald Leithner wrote: >>> Hi, >>> >>> my test stroage run out of diskspace. >>> >>> This happens at Version 0.8-11 >>> >>> I tried to forget the olders snapshots but this doesn't change the disk >>> usage. After this I started a manual GC (I assume it's garbage >>> collection). It failed after phase one with an error message. I didn't >>> copied the error message... (I miss the log panel in the gui). >>> >>> I also configured GC and Prune Schedules at the same time and told the >>> vm that backups to the pbs to keep only 20 copies. >>> >>> After a while I came back to the gui and has only 3 snapshots left and >>> one backup in progress (Thats maybe correct because of 1 yearly 1 >>> monthly 1 daily and 2 last). >>> The Statistics Tab still says 100% usage and "zfs list" lists the same >>> usage. >>> >>> Starting now a manual GC ends in the error message: >>> >>> unable to parse active worker status >>> 'UPID:backup-erlach3-test:00000400:0000036A:00000000:5F4CD753:termproxy= ::root:' >>> - not a valid user id >>=20 >> this was a known issue that should be fixed on upgrade to 0.8.11-1. can=20 >> you run 'grep termproxy /var/log/apt/term.log' on the PBS server? >>=20 >=20 > the only entry is "Fixing up termproxy user id in task log..." > btw. my first version was 0.8.9-1 not 0.8.11 I upgraded later to this > version >=20 >> you can fixup the task index by running the sed command from=20 >>=20 >> /var/lib/dpkg/info/proxmox-backup-server.postinst >>=20 >> which replaces the invalid user 'root' with the correct 'root@pam' >>=20 >=20 > ok after running the sed command manually the GC works again. >=20 > but is complains about no diskspace: >=20 > 2020-08-31T14:29:16+02:00: WARN: warning: unable to access chunk > 135e565dc79f80d3a9980688bfe161409bf229fb4d11ab7290b5b1e58b27bc63, > required by "/test3/vm/3011/2020-08-30T22:00:02Z/drive-scsi1.img.fidx" - > update atime failed for chunk > "/test3/.chunks/135e/135e565dc79f80d3a9980688bfe161409bf229fb4d11ab7290b5= b1e58b27bc63" > - ENOSPC: No space left on device if you don't have enough space to touch a chunk, that is rather bad..=20 you can attempt to free up some more space by deleting backup metadata=20 of snapshots you no longer needed, either by 'rm'-ing the directory that=20 represents them, or by using 'forget' on the GUI if that works.. what does 'df -m /test3' report? and/or the equivalent command for=20 whatever storage the datastore is on (e.g., zfs list -o space=20 path/to/dataset). =