From: David <david@blue-labs.org>
To: Frank de Lange <frank@unternet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: * Re: Severe trashing in 2.4.4
Date: Tue, 01 May 2001 15:11:58 -0700 [thread overview]
Message-ID: <3AEF34AE.3070601@blue-labs.org> (raw)
In-Reply-To: <20010501235046.A23616@unternet.org>
Can't say for a definite fact that it was reiserfs but I can say for a
definite fact that something fishy happens sometimes.
If I have a text file open, something.html comes to mind, If I edit it
and save it in one rxvt and open it in another rxvt, my changes may not
be there. If I save it *again* or exit the editing process, I will see
the changes in the second term. No, I'm not accidently forgetting to
save it, I know for a fact that I saved it and the first terminal shows
the non-modified state with the changes and the second term shows the
previous data.
Somewhere something is stuck in cache and what's on disk isn't what's in
cache and a second process for some reason gets what is on disk and not
what is in cache.
It happens infrequently but it -does- happen.
David
Frank de Lange wrote:
>Well,
>
>When a puzzled Alexey wondered whether the problems I was seeing with 2.4.4
>might be related to a failure to execute 'make clean' before compiling the
>kernel, I replied in the negative as I *always* clean up before compiling
>anything. Yet, for the sake of science and such I moved the kernel tree and
>started from scratch.
>
>The problems I was seeing are no more, 2.4.4 behaves like a good kernel should.
>
>Was it me? Was it reiserfs? Was is divine intervention? I will probably never
>find out, but for now this thread, and the accompanying scare, can Resquiam In
>Paces.
>
>Cheers//Frank
>
next prev parent reply other threads:[~2001-05-01 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 21:50 * Re: Severe trashing in 2.4.4 Frank de Lange
2001-05-01 22:11 ` David [this message]
2001-05-01 22:44 ` Chris Mason
2001-05-01 23:00 ` David S. Miller
2001-05-01 23:21 ` Frank de Lange
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=3AEF34AE.3070601@blue-labs.org \
--to=david@blue-labs.org \
--cc=frank@unternet.org \
--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