Processed: Re: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
Processing commands for cont...@bugs.debian.org: > severity 1032706 important Bug #1032706 [lxc] lxc-snapshot cannot restore containers with loop storage backend Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1032706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
severity 1032706 important thanks Hi, "Sperl, Mario" wrote on 11/03/2023 at 09:30:06+0100: > Package: lxc > Version: 1:5.0.2-1 > Severity: grave > Justification: causes data loss > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? I tried to generate a snapshot with > lxc-snapshot for a test container that is more than 1G of size. Snapshot > generation does not show any problems but the restore does only restore 1G so > the container is not able to start after restore. >* What exactly did you do (or not do) that was effective (or > ineffective)? One can create a new loop file with correct size and copy > the snapshot contents in here but this renders this command absolute useless > when using loop backend >* What was the outcome of this action? Container cannot start >* What outcome did you expect instead? A container that does start > normally after restoring. Lowering the severity for multiple reasons: 1. The data is not lost, only the changes after the latest snapshot are, as the snapshots are not deleted by a call to restore. The snapshot is actually a full-fledged lxc directory under snaps, that you can reuse almost directly. I admit not losing the changes after the latest snapshot would be better, but I feel that this sole point is not enough to keep the bug as 'grave'; 2. A snapshot should not be restored inplace, as suggested by the command's manpage. The -N option is only useful for restoration and allows one to create a new container based on the snapshot. It's actually this feature that doesn't work when the rootfs is on a loop device ; 3. This bug is tied specifically to a backend little to no user use, other filesystems seem to produce the proper result. If it comes to that, I'd rather remove the loop feature than having LXC out of bookworm. I'll still try to have a proper upstream solution offer before the release. -- PEB signature.asc Description: PGP signature
Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
I would suggest to add a note to https://github.com/lxc/lxc/issues/4289 to mention that LXC was kicked out from Bookworm due to this bug. Maybe they don't know. Regards Harri
Bug#1032706:
Control: forwarded -1 https://github.com/lxc/lxc/issues/4289 signature.asc Description: This is a digitally signed message part
Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
Hi Mathias, I submitted an issue on github: https://github.com/lxc/lxc/issues/4289 Step-by-step is explained there. Thank you, Mario On 3/11/23 17:59, Mathias Gibbens wrote: Hi Mario, I'm currently on travel with not-so-great network connectivity, so I haven't been able to reproduce this on my travel laptop, but will attempt to do so when I'm back from my trip. I expect that this issue will have to be forwarded to the lxc developers; if you want to do so you can submit an issue at https://github.com/lxc/lxc/issues, otherwise I'll so after reproducing the issue myself. To help ensure I'll be following exactly what you did, could you share the commands you used to setup the loop storage backend, the creation of the container, snapshoting, and attempted restoration of that snapshot? Thanks, Mathias
Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
Hi Mario, I'm currently on travel with not-so-great network connectivity, so I haven't been able to reproduce this on my travel laptop, but will attempt to do so when I'm back from my trip. I expect that this issue will have to be forwarded to the lxc developers; if you want to do so you can submit an issue at https://github.com/lxc/lxc/issues, otherwise I'll so after reproducing the issue myself. To help ensure I'll be following exactly what you did, could you share the commands you used to setup the loop storage backend, the creation of the container, snapshoting, and attempted restoration of that snapshot? Thanks, Mathias signature.asc Description: This is a digitally signed message part
Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend
Package: lxc Version: 1:5.0.2-1 Severity: grave Justification: causes data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to generate a snapshot with lxc-snapshot for a test container that is more than 1G of size. Snapshot generation does not show any problems but the restore does only restore 1G so the container is not able to start after restore. * What exactly did you do (or not do) that was effective (or ineffective)? One can create a new loop file with correct size and copy the snapshot contents in here but this renders this command absolute useless when using loop backend * What was the outcome of this action? Container cannot start * What outcome did you expect instead? A container that does start normally after restoring. -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii debconf [debconf-2.0]1.5.82 ii dnsmasq-base [dnsmasq-base] 2.89-1 ii iproute2 6.1.0-2 ii iptables 1.8.9-2 ii libapparmor1 3.0.8-3 ii libc62.36-8 ii libcap2 1:2.66-3 ii libgcc-s112.2.0-14 ii liblxc-common1:5.0.2-1 ii liblxc1 1:5.0.2-1 ii libseccomp2 2.5.4-1+b3 ii libselinux1 3.4-1+b5 ii lsb-base 11.6 ii nftables 1.0.6-2 ii sysvinit-utils [lsb-base]3.06-2 Versions of packages lxc recommends: ii apparmor 3.0.8-3 ii debootstrap1.0.128+nmu2 ii dirmngr2.2.40-1 ii gnupg 2.2.40-1 ii libpam-cgfs1:5.0.2-1 ii lxc-templates 3.0.4.48.g4765da8-1 ii lxcfs 5.0.3-1 ii openssl3.0.8-1 ii rsync 3.2.7-1 ii uidmap 1:4.13+dfsg1-1 ii wget 1.21.3-1+b2 Versions of packages lxc suggests: pn btrfs-progs ii lvm2 2.03.16-2 pn python3-lxc -- debconf information: lxc/auto_update_config:
