linux-ext4 - errors in ext4_mb_generate_buddy and ext4

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]

Date:	Sun, 08 May 2011 00:56:19 +0000
From:	Christoph Anton Mitterer <calestyo@...entia.net>
To:	<linux-ext4@...r.kernel.org>
Subject: errors in ext4_mb_generate_buddy and ext4_remount

Hi.

I've had several crashes recently, which lead to things like these:
May  6 00:23:53 heisenberg kernel: [   31.941036] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016253
May  6 00:23:53 heisenberg kernel: [   31.941049] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016250
May  6 00:23:53 heisenberg kernel: [   31.941073] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016249
May  6 00:23:53 heisenberg kernel: [   31.941106] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016248
May  6 00:23:53 heisenberg kernel: [   31.941120] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016247
May  6 00:23:53 heisenberg kernel: [   31.941135] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016240
May  6 00:23:53 heisenberg kernel: [   31.941158] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016239
May  6 00:23:53 heisenberg kernel: [   31.941168] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016238
May  6 00:23:53 heisenberg kernel: [   31.941174] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016237
May  6 00:23:53 heisenberg kernel: [   31.941180] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016236
May  6 00:23:53 heisenberg kernel: [   31.941190] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016235
May  6 00:23:53 heisenberg kernel: [   31.941200] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016234
May  6 00:23:53 heisenberg kernel: [   31.941212] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016233
May  6 00:23:53 heisenberg kernel: [   31.941217] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016232
May  6 00:23:53 heisenberg kernel: [   31.941228] EXT4-fs (dm-2):
ext4_orphan_cleanup: deleting unreferenced inode 2016231

... and some (at least to me) worrying questions during fsck.

However, I constantly get these errors:
[  331.744025] EXT4-fs (dm-2): error count: 10
[  331.744030] EXT4-fs (dm-2): initial error at 1304673122:
ext4_mb_generate_buddy:731
[  331.744034] EXT4-fs (dm-2): last error at 1304673124: ext4_remount:4250
... (probably) when reading some files. I guess it's reading files, at
least it happens during a debsums run (checks the package sums of more or
less all Debian packages installed).
Also the numbers in the errors above, are (at least until know, and as far
as I looked after it) the same.

It also happens (as far as I can see) only once, i.e. if the error has
already occurred, and I do e.g. my debsums again, it's not printed again.

fsck runs through fine (but quite quick; yes - of course - I've used -f)

Any ideas? (Please CC me as I'm off list).


Cheers,
Chris.


btw:
This (occuring in the host's kernel log and not the VM's)
[  325.655192] EXT4-fs (dm-2): Unaligned AIO/DIO on inode 1060986 by
VirtualBox; performance will be poor.
means that the blocks of the the guest are not aligned to the blocks of
the host, right?
But why is it only printed once?
--
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