Re: [PATCH] Re: 2.4.22-rc2 ext2 filesystem corruption

From: Martin Maney (maney_at_two14.net)
Date: 01/11/04

  • Next message: Gene Heskett: "Re: Q re /proc/bus/i2c"
    Date: 	Sat, 10 Jan 2004 17:18:40 -0600
    To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
    
    

    On Thu, Jan 08, 2004 at 10:25:08AM -0600, Martin Maney wrote:
    > On Sun, Jan 04, 2004 at 03:07:48AM +0100, Bartlomiej Zolnierkiewicz wrote:
    > > I see nothing in 2.4.23 which can explain this.
    > > Probably if you boot from Promise you will see corruption again.

    > that. In fact I did *not* observe the corruption when I booted from
    > the Promise, but I didn't have the same file (an XFree86 source

    Okay, color me as having no idea what's going on...

    Jiggered things around to boot from the drive connected to the Promise
    (hereafter the old drive) again, with a copy of the original test
    object (xfree86_4.2.1.orig.tar.gz from Branden's Debian archives). It
    still works with 2.4.23. Rebuilt 2.4.22 (didn't have any of the patches
    around, and I'm 99% sure I tested with 22-final just before giving up
    originally); that works too. Shutdown and physically removed the 3ware
    card from the machine; dug up the grub boot disk that I'd forgotten I
    would need for this, booted into 2.4.22 again. Still, it works.

    Maybe it's because the Promise chip knows it's no longer needed? :-/

    -- 
    ...and of course you must be careful not to overwrite the bounds of
    memory blocks, free a memory block twice, forget to free a memory block,
    use a memory block after it's been freed, use memory that you haven't
    explicitly allocated, etc.  We C++ programmers have developed tricks
    to help us deal with this sort of thing, in much the same way that people
    who suffer severe childhood trauma develop psychological mechanisms to
    insulate themselves from those experiences.  -- Joseph A. Knapka
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Gene Heskett: "Re: Q re /proc/bus/i2c"

    Relevant Pages

    • Re: X and intelfb fight over videomode
      ... > no framebuffer. ... The following is printed during boot: ... Ah, okay, you have a flatpanel display, so you really need vesa to program ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 64 bit kernel
      ... the chipset "fooled" the OS into thinking that it was doing 32 bit wide operations. ... kernel problem or if it's a BIOS problem. ... After some searching I found others with similar problems and they had to use "noapic nolapic" kernel boot options to install and boot the OS. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: RFC: [2.6 patch] better i386 CPU selection
      ... If we boot a 386 kernel on a ppro with that bug, ... For the handful of bytes saved in the mtrr driver, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • fastboot, diskstat
      ... that the total time for prefetching + actual boot was only 10% shorter, ... actually cache the pages I touched, ... Also, regarding the directory entries, are they accessed via the buffer ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: VST patches ported to 2.6.11-rc1
      ... Yes we want to boot with it disabled. ... >>Both of these arrays are kept as circular lists and read back such ... getting the VST sleeps he wants. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)