Hi Maks
On Fri, Feb 18, 2011 at 09:46:44AM +, maximilian attems wrote:
> On Fri, Feb 18, 2011 at 07:27:27AM +0100, Ola Lundqvist wrote:
> > Hi Maks
> >
> > Do you know when the next squeeze upload would be? Is it for the next
> > point release (and if so, do you know when that is?) or should
On Fri, Feb 18, 2011 at 07:27:27AM +0100, Ola Lundqvist wrote:
> Hi Maks
>
> Do you know when the next squeeze upload would be? Is it for the next
> point release (and if so, do you know when that is?) or should we try
> to convince the security team that this is actually a security issue.
>
> Da
Hi Maks
Do you know when the next squeeze upload would be? Is it for the next
point release (and if so, do you know when that is?) or should we try
to convince the security team that this is actually a security issue.
Data corruption is not a nice thing I would say...
// Ola
On Thu, Feb 17, 201
On Thu, 17 Feb 2011, Vladimir Kuklin wrote:
>
> git commit is here:
>
> http://git.openvz.org/?p=linux-2.6.32-openvz;a=commit;h=3e89668abca56e6e11e1bbb9cbac1008d3c2357b
>
> Please, don't forward it again to openvz devs. Just include it into
> patchset for 2.6.32-5-openvz kernel update.
it is i
There is a workaround for this bug at openvz git. Delayed allocation
must be turned off in order for OpenVZ container to start on ext4
filesystem.
See this
http://bugzilla.openvz.org/show_bug.cgi?id=1777
git commit is here:
http://git.openvz.org/?p=linux-2.6.32-openvz;a=commit;h=3e89668abca
5 matches
Mail list logo