Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
- To: Debian Bug Tracking System <email@example.com>
- Subject: Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
- From: "M. Dietrich" <firstname.lastname@example.org>
- Date: Wed, 27 Jan 2010 23:25:57 +0100
- Message-id: <email@example.com>
- Reply-to: "M. Dietrich" <firstname.lastname@example.org>, email@example.com
Justification: renders package unusable
my system had serious filesystem corruption with several -bigmem
kernel in the past (from 2.6.28 to 2.6.32).
git first discovered the problem because it complained about corruption
in the repo. a filesystem check found lots of double allocated blocks
and other problems.
i use a ext3 filesystem. i first thought its related to suspend/resume
so i didn't suspend anymore - file corruption still occured. so i
switched from a -bigmem kernel to a normal kernel with same version
and even after heavy usage (cross compile openwrt) no corruption was
for sure i can't guarantee that this isn't related to some hardware
fault like broken ram or the like but i checked ram with memtest86+.
please adjust Severity and/or Justification if i choosed that wrong.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash