Re: Bug#469293: vzctl: vzmigrate corrupts user-ids of files
Version: 3.0.22-1
Hi
I have now uploaded one new version for stable that fixes this critical issue.
It turned out that this problem was fixed, but not for stable.
Best regards,
// Ola
On Tue, Mar 04, 2008 at 02:24:37PM +0100, Christian Hofstaedtler wrote:
> Package: vzctl
> Version: 3.0.11-13
> Severity: critical
> Justification: causes serious data loss
>
> Hello!
>
> The vzmigrate script (etch Version) fails to use --numeric-ids with
> rsync, causing incorrect user-ids on the destination host, and therefore
> lots of broken stuff (in my case: ejabberd in the VE wouldn't start, because
> the ejabberd files were owned by another user).
>
> As this causes lots of pain, and loss of (meta-)data, setting Severity: critical.
>
> Upstream has patches for this:
> http://git.openvz.org/?p=vzctl;a=commitdiff;h=3a6a52665b15225ed2d10186861c00ce3b23b6be
> http://git.openvz.org/?p=vzctl;a=commitdiff;h=bb5138eb46abef2507dc0803d8f32642e44af9c3
>
> I think this would be worth patching in etch.
>
> Thanks,
> Christian
>
> -- System Information:
> Debian Release: 4.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.18-028stab053-dl3xx-openvz
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
>
> Versions of packages vzctl depends on:
> ii iproute 20061002-3 Professional tools to control the
> ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
> ii vzquota 3.0.8-2 server virtualization solution - q
>
> Versions of packages vzctl recommends:
> ii rsync 2.6.9-2etch1 fast remote file copy program (lik
>
> -- no debconf information
>
>
>
--
--------------------- Ola Lundqvist ---------------------------
/ opal@debian.org Annebergsslingan 37 \
| ola@opalsys.net 654 65 KARLSTAD |
| http://opalsys.net/ +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
Reply to: