RE: EXT3 filesystem corruption with kernel 2.6.32-bpo
Is there already a bug report filed for this in Debian or the Kernel list?
Reiner.
> -----Original Message-----
> From: P.S.S.Camp [mailto:P.S.S.Camp@kent.ac.uk]
> Sent: Wednesday, May 19, 2010 12:45 PM
> To: Buehl, Reiner
> Cc: backports-users@lists.backports.org
> Subject: RE: EXT3 filesystem corruption with kernel 2.6.32-bpo
>
>
> I have been seeing similar stuff I found disabling dir indexes and
> refscking the files systems help none this issue was still happening
> after 2.6.34.11, so I dont htink its bpo specific.
>
> Phill.
>
>
> On Wed, 19 May 2010, Buehl, Reiner wrote:
>
> > Memtest shows no error during multiple runs. Also two other RAID1 (on
> Western Digital disks) and a RAID5 (on a different type of Seagate
> disks) show no such errors.
> >
> > Any other ideas?
> >
> > Reiner.
> >
> >> -----Original Message-----
> >> From: backports-users-bounces@lists.backports.org [mailto:backports-
> >> users-bounces@lists.backports.org] On Behalf Of Stefan Bauer
> >> Sent: Tuesday, May 18, 2010 12:17 PM
> >> Cc: backports-users@lists.backports.org
> >> Subject: Re: EXT3 filesystem corruption with kernel 2.6.32-bpo
> >>
> >> Am 18.05.2010 12:04, Buehl, Reiner schrieb:
> >>> The two disks used in the RAID1 md device are both Seagate
> >> ST31000528AS
> >>> that show no errors in long and short SMART test and Seatools. How
> >> can
> >>> I fix this?
> >>
> >> Check your ram with memtest.
> >>
> >> Stefan
> >>
> >> --
> >> Stefan Bauer -----------------------------------------
> >> PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34
> >> -------- plzk.de - Linux - because it works ----------
> >
>
> --
> Senior Computer Science Computing Officer -- http://www.cs.kent.ac.uk/
> University Of Kent, Canterbury -- http://kent.ac.uk/
> Computer Science Systems -- http://www.cs.kent.ac.uk/systems/
> The Mirror Service -- http://www.mirrorservice.org/
Reply to: