From: Christian Ohm <chr.ohm@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: file corruption in 2.4.16/17
Date: Sat, 22 Dec 2001 23:02:24 +0100 [thread overview]
Message-ID: <20011222220223.GA537@moongate.thevoid.net> (raw)
hi.
i've recently bought a new 80gb ide drive, and am now getting corrupted
files on it. i've made three partitions for linux on it, a small ext2 one as
root, and two larger ones with reiserfs as /usr and /var. the problem is
that now some files get randomly corrupted; they are the right size, but
contain some random garbage (searching the archive for this list just came
up with some issues around july / kernel 2.4.6), which makes the system
pretty much unusable.
my old setup with a 20gb ide drive and a 4.5gb scsi drive worked flawlessly
for at least a year with reiserfs, so this seems to be a problem with
reiserfs and large drives (i haven't found a corrupted file on the ext2
partition (yet)). my hardware is: a nmc (now enmic) 8tax+ mainboard with via
kt133 chipset (newest bios), a maxtor d540x-4k 80gb harddrive and a quantum
lct15 20gb harddrive. i used kernel 2.4.16 with the preemtion patch, but
2.4.17 seems to have the same problem.
windows had a problem with the maxtor drive, too. i made a fat32 partition
and copied the files from the old drive under linux. worked perfectly, but
when reading the partition with windows, it showed a corrupted file system.
i had to install a special ide driver not included in the via 4in1 drivers
to read it correctly, but now it works without problems.
i'd be happy if there's a solution for this, as, like i said, the system now
is pretty much unusable.
bye
christian ohm
ps.: i'm not subscribed to this list, so please cc me on any replies to this
thread. thanks.
next reply other threads:[~2001-12-22 22:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 22:02 Christian Ohm [this message]
[not found] ` <01122300525700.01910@manta>
2001-12-22 23:06 ` file corruption in 2.4.16/17 Christian Ohm
[not found] ` <Pine.LNX.4.33.0112222109310.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-23 2:57 ` Christian Ohm
[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=20011222220223.GA537@moongate.thevoid.net \
--to=chr.ohm@gmx.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox