From: Oleg Drokin <green@namesys.com>
To: Fabio Fracassi <turiya@linuxfromscratch.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Complete lockup when using g++ on reiserfs
Date: Mon, 21 Jan 2002 16:51:03 +0300 [thread overview]
Message-ID: <20020121165103.A4915@namesys.com> (raw)
In-Reply-To: <16Sckv-03IJKyC@fmrl01.sul.t-online.com>
In-Reply-To: <16Sckv-03IJKyC@fmrl01.sul.t-online.com>
Hello!
On Mon, Jan 21, 2002 at 12:41:02PM +0100, Fabio Fracassi wrote:
> I suppose the Problem is somewhere in the ReiserFs part, since when this hang
> happens the last processed c++ file sometimes gets corrupted.
I won;t be so sure about that.
It may be that hang appears elsewhere, and reiserfs just have no time
to fill allocated data block with meaningful data.
Reiserfs does not offer data journaling, so only metadata consistiency is
there.
What you are describing looks more like faulty hardware.
Bye,
Oleg
prev parent reply other threads:[~2002-01-21 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 11:41 Complete lockup when using g++ on reiserfs Fabio Fracassi
2002-01-21 13:51 ` Oleg Drokin [this message]
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=20020121165103.A4915@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=turiya@linuxfromscratch.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