| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4803E41C.1080003@rtr.ca> Date: Mon, 14 Apr 2008 19:09:16 -0400 From: Mark Lord <lkml@....ca> To: Eric Sandeen <sandeen@...hat.com> Cc: linux-ext4@...r.kernel.org, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: ext3: Freeing blocks not in datazone Eric Sandeen wrote: > Mark Lord wrote: >> Eric Sandeen wrote: >>> Mark Lord wrote: >>>> One of my test systems here, running 2.6.25-rc8-git*, >>>> just now crapped out with this in the tail end of dmesg: >>>> >>>> [ 20.927780] EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks not in datazone - block >>>> [ 20.928756] Aborting journal on device sda1. >>> I've got a similar report from the F9 installer, also on 2.6.25-rc8* ... >>> trying to reproduce locally. >> .. >> >> Well, if it's of any help, here it was on a 2.4GHz Intel QuadCore, >> 32-bit kernel/userspace, 4GB RAM, PAE-enabled. > > Any chance you had done a resize2fs, online or offline, before this? > Just a guess based on the installer thing I'm looking at... .. No, nothing really special there. It's just a single drive / single filesystem (K)Ubuntu install originally, with various test 2.6.25-rc* kernels being substituted in. There are lots of other drives in the box for driver development, but they have nothing to do with the ext3 root fs. My guess would be that the 4 fast CPU cores managed to race on something. Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists