From: Christian Ohm <chr.ohm@gmx.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: file corruption in 2.4.16/17
Date: Sun, 23 Dec 2001 03:57:52 +0100 [thread overview]
Message-ID: <20011223025752.GA20445@moongate.thevoid.net> (raw)
In-Reply-To: <20011222220223.GA537@moongate.thevoid.net> <Pine.LNX.4.33.0112222109310.5312-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0112222109310.5312-100000@coffee.psychology.mcmaster.ca>
> there is no problem with these disks or chipsets. have you checked your
> ide cable (*always* must be 18" or less, with *both* ends plugged in)?
> also, do you have the via-specific ide driver?
the ide cable is the one that came with the mainboard, it worked perfectly
for one year with the 20gb hd. and yes, i'm using the via-driver.
the strange thing about this is that it all worked perfectly before i added
the 80gb disk. and it corrupts files only on that disk.
anyway, i've recompiled 2.4.17 from a fresh source tree. until now, i
haven't discovered any corrupted files of whoch i _know_ that they have to
be corrupted since i used this kernel. so probably this was a problem of the
preemption patch and reiserfs and large disks and via chipsets, but i'm not
100% sure about this. the changelog for 2.4.17 mentioned some reiserfs
fixes; are any of those related to corrupted files?
bye
christian ohm
next prev parent reply other threads:[~2001-12-23 4:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 22:02 file corruption in 2.4.16/17 Christian Ohm
[not found] ` <01122300525700.01910@manta>
2001-12-22 23:06 ` Christian Ohm
[not found] ` <Pine.LNX.4.33.0112222109310.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-23 2:57 ` Christian Ohm [this message]
[not found] ` <Pine.LNX.4.33.0112230110110.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-24 1:04 ` Christian Ohm
[not found] ` <Pine.LNX.4.33.0112232355540.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-25 0:39 ` Christian Ohm
[not found] ` <01122510384005.01845@manta>
2001-12-26 0:59 ` Christian Ohm
2001-12-23 6:48 ` Andre Hedrick
2001-12-23 13:39 ` Alan Cox
2001-12-24 1:12 ` Christian Ohm
2001-12-24 9:17 ` Hans Reiser
2001-12-25 0:44 ` Christian Ohm
2001-12-25 10:23 ` Hans Reiser
2001-12-26 0:53 ` Christian Ohm
2001-12-26 6:20 ` Oleg Drokin
2001-12-27 3:09 ` Christian Ohm
2001-12-27 11:06 ` Hans Reiser
2001-12-28 0:24 ` Christian Ohm
2001-12-28 1:32 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011223025752.GA20445@moongate.thevoid.net \
--to=chr.ohm@gmx.net \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.