From: Philippe <rouquier.p@wanadoo.fr>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs 3.6 problem with test9
Date: Wed, 12 Nov 2003 19:51:16 +0100 [thread overview]
Message-ID: <1068663075.17051.12.camel@Genesyme> (raw)
In-Reply-To: <87smkt63xu.wl@drakkar.ibe.miee.ru>
Le mer 12/11/2003 à 15:45, Samium Gromoff a écrit :
> > > Last time I had a box with similar problems it was memory. I'd put
> > > your system through a memtest.
> >
> > thanks for your answer.
> > I did as you said but no problem (memtest 3.0).
>
> For how long did you run the test?
>
> It is known that often a 24-hour memtest is not enough to find real world
> memory failures.
>
> Also it is known that gcc (yeah you`ll wonder) is much better at finding them,
> so there`s the question: do you compile stuff often, and if so, whether
> gcc bails out with "internal error" messages sometimes?
>
> Also, if i were you i would do the following:
>
> bash-2.05b$ dd if=/dev/urandom of=test bs=1048576 count=1024
> bash-2.05b$ bzip2 test
> bash-2.05b$ bunzip2 test.bz2
>
> And if you have a memory failure bzip2 checksumming would show that up on the
> bunzip2 stage.
>
> regards, Samium Gromoff
thanks for your answer.
I ran memtest for a whole night yesterday (again) : nothing.
I have never had any problem with gcc. execpt that sometimes after a big
compiling I have some files damaged but _they_are_not_the_ones_used_
by_gcc_. they always are in another directory.
I ran the test with dd and bzip2 : no problem.
Yet I'm afraid it is too late. I switched to ext3 today as my all system
was gradually becoming unusable after compiling large apps. I was fed up
with rebuilding partitions.
Now, it runs fine. but it might not mean anything about my hardware ...
I 'll try this.
Anyway I'm willing to explore the problem; in particular because some
other people seem to have the same problem.
Moreover reiserfs is faster. I liked it and I'd like to come back to it.
Note: I kept the original reiserfs partition with the errors. So if
someone needs any log to figure out where the problem comes from I have
everything at hand. I'm also willing to perform other tests.
regards.
Philippe Rouquier.
next prev parent reply other threads:[~2003-11-12 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 14:45 Samium Gromoff
2003-11-12 18:51 ` Philippe [this message]
2003-11-12 22:35 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 12:19 Philippe
2003-11-11 13:59 ` Ragnar Hojland Espinosa
2003-11-11 17:33 ` Philippe
2003-11-12 10:36 ` Philippe
2003-11-11 16:59 ` bill davidsen
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=1068663075.17051.12.camel@Genesyme \
--to=rouquier.p@wanadoo.fr \
--cc=deepfire@ibe.miee.ru \
--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
Powered by JetHome