[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#567204: marked as done (linux-image-686-bigmem: serious filesystem corruption with bigmem kernels)

Your message dated Thu, 25 Feb 2010 17:56:07 +0100
with message-id <20100225165607.GA2456@galadriel.inutil.org>
and subject line Re: Bug#567204: serious filesystem corruption with bigmem kernels
has caused the Debian Bug report #567204,
regarding linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
567204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567204
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-686-bigmem
Severity: grave
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
found.

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

--- End Message ---
--- Begin Message --- 
On Thu, Feb 25, 2010 at 11:30:38AM +0100, M. Dietrich wrote:
> On Thu, Feb 18, 2010 at 01:21:22AM +0000, Ben Hutchings wrote:
> > On Mon, 2010-02-01 at 15:55 +0100, M. Dietrich wrote:
> > > Package: linux-image-686-bigmem
> > > Severity: normal
> > > 
> > > i started a reportbug run with the real kernel name. this is the
> > > outcome:
> > 
> > I can't see any obvious suspect here.  Therefore, please file a bug
> > report upstream at <http://bugzilla.kernel.org>, selecting product
> > 'Platform Specific/Hardware', component 'i386', and providing the same
> > information in your report here.  Let us know the bug number so we can
> > track it.
> 
> close the bug
> 
> i encountered file system corruption with a non-bigmem kernel today
> 
> i don't now what's going on & will now check the hd

Ok, closing.

Cheers,
        Moritz

--- End Message ---
Reply to: