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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 59E40691E9 for ; Tue, 4 Aug 2020 18:08:52 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3AC82EC76 for ; Tue, 4 Aug 2020 18:08:52 +0200 (CEST) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 C368FEC5F for ; Tue, 4 Aug 2020 18:08:50 +0200 (CEST) Received: by mail-lj1-x22c.google.com with SMTP id z14so6618976ljm.1 for ; Tue, 04 Aug 2020 09:08:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7pK/5L+McLW7Y5D88jpRbYSVtBeD6wyPrlhF1TRj+Bs=; b=jJGUwrS/JdHwZSx7sQkWn7KSLglJGq6Znq1+9SLgZtrCfSz2jFM5r7Qw8c4DftKmVW Wivb7EMgbMT2ERP4xzsCaHIpRbz7ze9dwyL/UeLOhsIbB+uJlZYmap8Mxzbkp3plcWgM 8EZpg3cgqoAaLIB6zJefq0oIQfmH0I7rxMVnlvCBte9bEI9DVGqchgFuRavDnIeevsGI jH02Ql8Yc7E71XnBwX+RvuLusdfv7Hb1MmNrZNGYxTWGwa+yA38Cc0X1K3+q7VebxqIw eBP6cRRWSEDXdRVfWxzuylogUTMzv2C98qS6aXy0OXi34/HjxK2r7ifdL0vyBtdI+7mx TWyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7pK/5L+McLW7Y5D88jpRbYSVtBeD6wyPrlhF1TRj+Bs=; b=eaaR4WphxQRXALkWaeKdsSdp9P3Oy+G8FiaUxq/0tuUUhkNYY6ECwQZOnIBF2XcLDR aKBPBm2wibgdO9Pqj3kc5ZyUzMcZzxcjNqKDXxcM9RmAHpqQhi8GEiBjy0b5levp56dm I1/R/Y7pzQosYlEDtinsLyZsd590MUzTbwVWsiDAqeDO4c0XFADVHCE2cQMftPcqk9v1 BYewyrhGxqpJu64BOh/lHcxUdGy1EQylfHGhN8KEp53qPVMtsSqn6/hRAEvI8dQ9P5YY Xe2A5aL2cAYYl1iP9u+5XN39Er6f085MNNCyCzehfnubxiSG80a0mT0O0FsdM0kraTO0 7MlQ== X-Gm-Message-State: AOAM531CNA8c+KSXN+LAis971jsgdnz9fF1wrCOnyQeheuugq7lSZJbF 764tnSIxbt6p1gdXj9R+bRNl0p+RLmxWwYSCmnFp9zbHYg0= X-Google-Smtp-Source: ABdhPJxGQI0ZknkWLj6KUxNWRNCR+BglJ9x/DGqjCdPGQkzEo3/KOHWRxQC/H9iid9M3SV0/PPFaMOkr5lprqLkmFRk= X-Received: by 2002:a2e:b4e1:: with SMTP id s1mr9820817ljm.433.1596557323503; Tue, 04 Aug 2020 09:08:43 -0700 (PDT) MIME-Version: 1.0 References: <20200725125208.GA24275@lilliput.linux.it> <20200804122204.GB20062@lilliput.linux.it> In-Reply-To: <20200804122204.GB20062@lilliput.linux.it> From: Yannis Milios Date: Tue, 4 Aug 2020 17:08:32 +0100 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Temporary add a node to a cluster... X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2020 16:08:52 -0000 On Tue, 4 Aug 2020 at 13:30, Marco Gaiarin wrote: > > root@phisrita:~# zfs list -t snapshot > NAME USED AVAIL REFER > MOUNTPOINT > rpool/data/vm-100-disk-0@--head-- 116M - 6.19G - > rpool/data/vm-100-disk-1@--head-- 2.31M - 13.2G - > rpool/data/vm-100-disk-2@--head-- 2.29M - 31.6G - > > They can harm? How can i get rid of these? > I'm not sure how those snapshots were created, perhaps they exist on the source (or were created automatically by your zfs replication tool) ? Anyhow it shouldn't harm if you just use 'zfs destroy' to remove the snapshots if you do not need them. The important part would be to check if that VM is running properly on its new host (and of course back it up somewhere else just in case something goes wrong). Y.