From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Marco Gaiarin <gaio@lilliput.linux.it>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Leftover replication snapshots?!
Date: Wed, 30 Jul 2025 17:17:16 +0200 [thread overview]
Message-ID: <qkppll-jc62.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <adckkl-f8b1.ln1@leia.lilliput.linux.it>; from SmartGate on Wed, Jul 30, 2025 at 22:36:01PM +0200
Mandi! Marco Gaiarin
In chel di` si favelave...
> But snapshot get not deleted. Why?
I reply myself: these ssnapshot are aevidently an 'internal tool' to manage
replication.
> If i need temporary some space, can i safely delete all these snapshot
> (clerly by hand, via 'zfs destroy')?
No, these snapshot cannot be deleted, replica simply stop in error
if missing.
If deleted, the entire volume have to be deleted (in the destination replica,
of course) and replica have to be started by zero.
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-07-30 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:44 Marco Gaiarin
2025-07-30 15:17 ` Marco Gaiarin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=qkppll-jc62.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox