From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage 1/1] add check for fsfreeze before snapshot
Date: Thu, 5 Nov 2020 19:00:32 +0100 [thread overview]
Message-ID: <7a96af02-544b-eb82-b1a1-185b323c24d8@proxmox.com> (raw)
In-Reply-To: <20201105160631.26834-3-s.ivanov@proxmox.com>
On 05.11.20 17:06, Stoiko Ivanov wrote:
> In order to take a snapshot of a container volume, which can be mounted
> read-only with RBD, the volume needs to be frozen (fsfreeze (8)) before taking
> the snapshot. Only RBD is affected by this (for LVMThin this is handled
> by the devicemapper).
>
> This commit adds helpers to determine if the FIFREEZE ioctl needs to be called
> for the volume.
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> PVE/Storage.pm | 12 ++++++++++++
> PVE/Storage/Plugin.pm | 4 ++++
> PVE/Storage/RBDPlugin.pm | 5 +++++
> 3 files changed, 21 insertions(+)
>
> diff --git a/PVE/Storage.pm b/PVE/Storage.pm
> index cd7b5ff..27223b6 100755
> --- a/PVE/Storage.pm
> +++ b/PVE/Storage.pm
> @@ -287,6 +287,18 @@ sub volume_snapshot_delete {
> }
> }
>
> +# check if a filesystem on top of a volume needs to flush it's journal for
> +# constency (see fsfreeze(8)) before a snapshot is taken - needed for
> +# container mountpoints
> +sub volume_snapshot_needs_fsfreeze {
> + my ($cfg, $volid) = @_;
> +
> + my ($storeid, $volname) = parse_volume_id($volid);
> + my $scfg = storage_config($cfg, $storeid);
> + my $plugin = PVE::Storage::Plugin->lookup($scfg->{type});
> + return $plugin->volume_snapshot_needs_fsfreeze();
> +}
> +
> # check if a volume or snapshot supports a given feature
> # $feature - one of:
> # clone - linked clone is possible
> diff --git a/PVE/Storage/Plugin.pm b/PVE/Storage/Plugin.pm
> index 63f68da..a046640 100644
> --- a/PVE/Storage/Plugin.pm
> +++ b/PVE/Storage/Plugin.pm
> @@ -888,6 +888,10 @@ sub volume_snapshot_delete {
> return undef;
> }
>
> +sub volume_snapshot_needs_fsfreeze {
expanding the storage plugin ABI should normally be recorded via the version/
age mechanism. New additions which do not break existing plugins should bump
both, max age and version. Else, external plugins cannot know if they can rely
on that method.
> +
> + return 0;
> +}
> sub storage_can_replicate {
> my ($class, $scfg, $storeid, $format) = @_;
>
> diff --git a/PVE/Storage/RBDPlugin.pm b/PVE/Storage/RBDPlugin.pm
> index 38f2b46..94df89d 100644
> --- a/PVE/Storage/RBDPlugin.pm
> +++ b/PVE/Storage/RBDPlugin.pm
> @@ -694,6 +694,11 @@ sub volume_snapshot_delete {
> return undef;
> }
>
> +sub volume_snapshot_needs_fsfreeze {
> +
> + return 1;
> +}
> +
> sub volume_has_feature {
> my ($class, $scfg, $feature, $storeid, $volname, $snapname, $running) = @_;
>
>
next prev parent reply other threads:[~2020-11-05 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:06 [pve-devel] [PATCH common/storage/container] add fsfreeze/thaw for rbd snapshots Stoiko Ivanov
2020-11-05 16:06 ` [pve-devel] [PATCH common] add fsfreeze helper: Stoiko Ivanov
2020-11-05 16:06 ` [pve-devel] [PATCH storage 1/1] add check for fsfreeze before snapshot Stoiko Ivanov
2020-11-05 18:00 ` Thomas Lamprecht [this message]
2020-11-05 16:06 ` [pve-devel] [PATCH container 1/1] snapshot creation: fsfreeze mountpoints, if needed Stoiko Ivanov
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=7a96af02-544b-eb82-b1a1-185b323c24d8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.