From: Thomas <thomas@lgy.fr>
To: Stoiko Ivanov <s.ivanov@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [Allow snapshot backup with glusterfs 0/1]
Date: Sat, 14 Nov 2020 01:31:10 +0100 [thread overview]
Message-ID: <ccc2c618e95114d4c1168e0848eb74107f13ce57.camel@lgy.fr> (raw)
In-Reply-To: <20201113151210.02c9de62@rosa.proxmox.com>
Hi
Thank for your review.
When i backup lxc with glusterfs mount point, backup never finish.I
understant that you can disableit without rationale and maybe it's a
bad way to resolve this issue.I need to create ticket in bugzilla?
on function sync_container_namespace the bellow loop is never
exit.while (waitpid($child, 0) != $child) {}
There is no fail and no error message.
When i use bash command in lxc "sync /mount/point" there is no
issue.But
You can find bellow step to reproduce :
---------------------------------------create lxc with name g1 with -
debian 10 template - on lvmthin pool storage - privilegied conteneur -
dhcp for configuration phase - exemple lxc id = 125
LXCG1=125LXCG2=126
pct start $LXCG1pct enter $LXCG1apt-get updateapt install glusterfs-
server -yapt cleansystemctl enable glusterd mkdir -p /data/glusterfs
#add the 2 line in /etc/hostscat << EOF >> /etc/hosts10.10.10.1
g1 10.10.10.2 g2 EOF
poweroff
pct clone $LXCG1 $LXCG2 --hostname g2pct set $LXCG1 --net0
name=eth0,bridge=vmbr0,ip=10.10.10.1/24pct set $LXCG2 --net0
name=eth0,bridge=vmbr0,ip=10.10.10.2/24pct set $LXCG1 --features
fuse=0,mknod=0
pct start $LXCG1pct start $LXCG2pct enter $LXCG1gluster peer probe
g2gluster volume create glusterfsvolume replica 2 g1:/data/glusterfs
g2:/data/glusterfs forcegluster volume start glusterfsvolume
mkdir /mnt/tmp/mount -t glusterfs g1:/glusterfsvolume /mnt/tmp
vzdump $LXCG2 #work
vzdump $LXCG1 #never finish------------------------------------------
---
Le vendredi 13 novembre 2020 à 15:12 +0100, Stoiko Ivanov a écrit :
> Hi,
> Thank you for contributing to PVE!
> Could you explain what the patch fixes and why it works (would also
> begreat to have that information in the commit-message)?I checked our
> bugzilla and the community forum, but could not find anyrecent issue
> regarding gluster and containers (I probably overlooked it).
> AFAICT the patch disables running syncfs(2) on the gluster fuse-mount
> usedfor containers. Does the syncfs call fail? What error do you
> get?The syncfs call is there to ensure that the backup is consistent
> as far aspossible - so I would not disable it without rationale.
> On another note - we would need a signed CLA from you, in order to be
> ableto include your code in our codebase - see [0].
> Best Regards,stoiko
> [0]
> https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
>
> On Thu, 12 Nov 2020 19:48:38 +0100Thomas Legay <thomas@lgy.fr> wrote:
> > Thomas Legay (1): Allow LXC snapshot backup with glusterfs mount
> > point
> > src/PVE/LXC.pm | 1 + 1 file changed, 1 insertion(+)
prev parent reply other threads:[~2020-11-14 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 18:48 Thomas Legay
2020-11-12 18:48 ` [pve-devel] [PATCH pve-container] Allow LXC snapshot backup with glusterfs mount point Thomas Legay
2020-11-13 14:12 ` [pve-devel] [Allow snapshot backup with glusterfs 0/1] Stoiko Ivanov
2020-11-14 0:31 ` Thomas [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=ccc2c618e95114d4c1168e0848eb74107f13ce57.camel@lgy.fr \
--to=thomas@lgy.fr \
--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.