Re: 2.4.22-rc2 ext2 filesystem corruption

From: Martin Maney (maney_at_two14.net)
Date: 08/12/03

  • Next message: Andrew Morton: "Re: data corruption using raid0+lvm2+jfs with 2.6.0-test3" 
    Date:	Tue, 12 Aug 2003 16:36:45 -0500
To: Marcelo Tosatti <marcelo@conectiva.com.br>

    On Tue, Aug 12, 2003 at 02:09:53PM -0300, Marcelo Tosatti wrote:
    > Well, rc2 had a Promise change. I'm not sure if it could be the cause, but
    > lets check.

    > Please try -rc2 with the following patch unpplied (patch -R):

    Oops, I overlooked the change. Tried it with a relatively
    stripped-down 22-rc2 build (slimmed the vmlinuz down by about 100K),
    but that made no difference. I popped a CMD648-based card in, disabled
    the on-board Promise chip, and it booted right up and works fine with
    22-rc2. So if the .id -> .present is the only change that affected the
    Promise driver (I did some looking for obvious, but gave up after
    realizing that unless the change actually had a /* borks Promise IDE
    controllers*/ in it I wouldn't be likely to recognize it), then I guess
    that's it.

    > # [PATCH] PATCH: Promise cable
    > #
    > # The old driver used to check .id was NULL to detect drive absent
    > # (which is wrong but generally worked) with the IDE changes it always
    > # got it wrong. This fixes it to test .present instead.
    > #
    > # Without this fix it mistakenly assumes that the empty drive slot
    > # cannot do UDMA66/100/133

    Does this really mean that the Promise has been running at only 33MHz
    all along, and that with this fix it stopped choking the speed and
    that's the cause of the problem? I know that back when I first setup
    this drive on the Promise (over a year ago - I'm pretty sure I was
    runnign 2.2.latest back then and had to jumper the drive to get around
    the 64K cylinders problem) I know I saw transfer speeds greater than
    33MB reported by hdparm -T.

    Okay, for completeness I should back out that change and retest it with
    the Promise, and I'll try to remember to throw a quick throughput test
    in just to see what it's been doing to me. ;-)

    BTW, yes, I am (and have been) using an 80-pin cable with this drive. 

    -- 
Faced with the choice between changing one's mind and proving there is
no need to do so, almost everyone gets busy on the proof. -- JKG
-
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: Andrew Morton: "Re: data corruption using raid0+lvm2+jfs with 2.6.0-test3"

    Relevant Pages