linux-kernel - ext3: Freeing blocks not in datazone

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4803A109.5080800@rtr.ca>
Date:	Mon, 14 Apr 2008 14:23:05 -0400
From:	Mark Lord <lkml@....ca>
To:	linux-ext4@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: ext3: Freeing blocks not in datazone 

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.
[    7.336461] ext3_abort called.
[   20.930208] Remounting filesystem read-only
[    7.336925] EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
[    7.336930] Remounting filesystem read-only
[   20.930847] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[   20.930960] EXT3-fs error (device sda1) in ext3_truncate: Journal has aborted
[   20.931037] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[   20.931148] EXT3-fs error (device sda1) in ext3_orphan_del: Journal has aborted
[   20.931257] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[   20.932057] __journal_remove_journal_head: freeing b_committed_data
[   20.932071] __journal_remove_journal_head: freeing b_committed_data
[   20.932165] __journal_remove_journal_head: freeing b_committed_data
[   20.932185] __journal_remove_journal_head: freeing b_committed_data
[   20.932197] __journal_remove_journal_head: freeing b_committed_data

I had just booted the system, and was simultaneously doing "rm -r" on an old kernel tree
while also doing mirrordir to refressh a different kernel tree from a master copy off NFS.

Not much else to say.  e2fsck seems to have recovered things,
and I've repeated the commands successfully after rebooting.

-ml
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/