From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <d.jaeger@proxmox.com> 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 54A4774138 for <pve-devel@lists.proxmox.com>; Mon, 21 Jun 2021 09:06:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 46BDC185C7 for <pve-devel@lists.proxmox.com>; Mon, 21 Jun 2021 09:06:13 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id A0C0C185B8 for <pve-devel@lists.proxmox.com>; Mon, 21 Jun 2021 09:06:11 +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 6D84440574 for <pve-devel@lists.proxmox.com>; Mon, 21 Jun 2021 09:06:05 +0200 (CEST) Date: Mon, 21 Jun 2021 09:06:07 +0200 From: Dominic =?iso-8859-1?Q?J=E4ger?= <d.jaeger@proxmox.com> To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <20210621070607.GA8754@mala.proxmox.com> References: <20210521104448.4376-1-d.jaeger@proxmox.com> <c03517a4-82a4-6955-861f-0b9f7505fb71@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <c03517a4-82a4-6955-861f-0b9f7505fb71@proxmox.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-SPAM-LEVEL: Spam detection results: 0 AWL 1.354 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH docs] pvesm: How to remove directory storages X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Mon, 21 Jun 2021 07:06:13 -0000 On Fri, Jun 18, 2021 at 06:31:51PM +0200, Thomas Lamprecht wrote: > On 21.05.21 12:44, Dominic Jäger wrote: > > Users are repeatedly left with entries in Disks->Directory, most recently > > https://forum.proxmox.com/threads/how-to-remove-local-directory-storage-properly.89504/ > > > > Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com> > > --- > > pve-storage-dir.adoc | 13 +++++++++++++ > > 1 file changed, 13 insertions(+) > > > > diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc > > index 090a44b..8489b42 100644 > > --- a/pve-storage-dir.adoc > > +++ b/pve-storage-dir.adoc > > @@ -133,6 +133,19 @@ And you can remove the image with: > > > > # pvesm free local:100/vm-100-disk10.raw > > > > +To completely remove a directory storage with the name `backup`, > > + > > +1. Remove the storage from `/etc/pve/storage.cfg` > > + > > + # pvesm remove backup > > + > > +2. Stop & disable the systemd mount > > + > > + # systemctl disable mnt-pve-backup.mount --now > > + > > +3. Remove the systemd mount file > > + > > + # rm /etc/systemd/system/mnt-pve-backup.mount > > shouldn't the disable --now already take care of that? > I expected something similar, but when I tried it out, the entry remained always visible in the GUI without the `rm`. > > > > ifdef::wiki[] > > > > >