Date: Fri, 18 Nov 2011 20:50:23 +0400 From: Solar Designer <solar@...nwall.com> To: owl-dev@...ts.openwall.com Subject: Re: kernel update? ext4 issues On Fri, Nov 18, 2011 at 08:31:20PM +0400, (GalaxyMaster) wrote: > On Fri, Nov 18, 2011 at 08:18:18PM +0400, Solar Designer wrote: > > Ouch. I doubt that you were hit by this specific bug. Can you provide > > more detail on the symptoms? Did you have a file of almost exactly 4 GB? > > Yes, this is the case. The file was InnoDB tablespace and was 4GB. I'm > quite confident that I encountered the mentioned bug. The symptoms were > that the server became unreachable by ssh and it's console was saying > that ext4 code failed to allocate a block (this was in a loop). This doesn't sound like the specific bug you referred to. For that one, I'd expect just one error message and kernel panic. But I could be wrong. > Unfortunately, I don't recall the exact error message, but when I > investigated that I was quite sure that the crash was the result of the > bug I mentioned in the original post. > > > What kernel version were you running? > > CentOS 2.6.18-274.3.1.el5xen (but IIUC it's the same ext4 code as the > kernel we have in Owl). Yes. > > (There were ext4 fixes before > > -274 as well, so maybe the bug that you hit is already fixed in our > > current kernel.) > > RH fixed a lot of off by 1 ext4 issues in 274.4.1, so I doubt that our > kernel contains them. All I meant was that other ext4 bugs were fixed in pre-274 kernels, but since you say you had -274.3.1.el5xen this means that we likely have that same bug that you hit, too. Yes, we need to update. Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.