public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Ohm <chr.ohm@gmx.net>
To: Hans Reiser <reiser@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file corruption in 2.4.16/17
Date: Fri, 28 Dec 2001 01:24:12 +0100	[thread overview]
Message-ID: <20011228002412.GA691@moongate.thevoid.net> (raw)
In-Reply-To: <20011222220223.GA537@moongate.thevoid.net> <3C26F2AC.1050809@namesys.com> <20011225004459.GB3752@moongate.thevoid.net> <3C285384.3020302@namesys.com> <20011226005327.GA3970@moongate.thevoid.net> <20011226092024.A871@namesys.com> <20011227030946.GA472@moongate.thevoid.net> <3C2B00B3.4040505@namesys.com>
In-Reply-To: <3C2B00B3.4040505@namesys.com>

On Thu, Dec 27, 2001 at 02:06:27PM +0300, Hans Reiser wrote:
> It sounds like you get reiserfs corruptions easily, without crashing the 
> machine or anythin unusual, and in that case you surely have hardware 
> problems.  Please note in our FAQ the discussion of how reiserfs runs 
> hotter than ext2, and it is common for improperly cooled CPUs to work 
> well for ext2 and not reiserfs (tail combining heats the CPU).

not likely; its a duron 700 and lm-sensors says < 37 degree celsius with
open case (as it is now) and about 45 with closed case.

anyway, i've created a new fat32 partition where the old reiserfs one was,
copied lots of files to it and diffed them. no difference. i copied the same
files as earlier to the new reiserfs partition and diffed them. no
difference. no other corrupted files elsewhere, as far as i have seen now.
so whatever was the cause of this seems to have gone now (always the same
kernel, nothing changed with the hardware). perhaps the reiserfs file system
structure got corrupted somehow and thus caused this. don't know. if i have
nothing else to do, i'll create another reiserfs partition where the old one
was and try to corrupt some files.

i'll report back if i get corrupted files again. until then, thanks to
everyone trying to help me and sorry for taking your time.

bye
christian ohm

  reply	other threads:[~2001-12-28  0:24 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
     [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 [this message]
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=20011228002412.GA691@moongate.thevoid.net \
    --to=chr.ohm@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    /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