All of lore.kernel.org
 help / color / mirror / Atom feed
From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: link/unlink problem gone?
Date: 6 Feb 2003 17:32:10 -0500	[thread overview]
Message-ID: <b1unpa$bmb$1@satsuki.furryterror.org> (raw)
In-Reply-To: 20030131105745.A7426@namesys.com

In article <20030131105745.A7426@namesys.com>,
Oleg Drokin  <green@namesys.com> wrote:
>Hello!
>
>   Sigh, these were false hopes indeed.
>   I can reproduce it with 2.4.21-pre4, only it is now harder for some reason.

I've seen times-to-failure ranging from 20 minutes to 20+ hours (!).

Interestingly enough, both extremes occurred back-to-back--I tried
for 20 hours to reproduce the problem, failed, tried again with the
same kernel setup, and 20 minutes later the machine was spewing out
"Permission denied" too quickly to display.

>   Chris: My current idea is it happens during low memory conditions, so I am
>   actively running around prune_icache and id's dcache equivalent. Probably
>   you can easily reproduce that if you'd have no swap and not very much RAM.
>
>   (Ok, I just checked, limited the RAM to 90M and turned off SWAP entirely.
>    and reproduced the problem fairly quickly)

I have observed the problem on machines ranging in size from 96 to
512MB RAM.  I haven't observed a correlation between swapping activity
and failures but I haven't been looking for this either.  The machines
that have problems machines are swapping at some time or another (they
have several hundred MB of swap used).

-- 
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD

       reply	other threads:[~2003-02-06 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030129164906.A8320@namesys.com>
     [not found] ` <20030131105745.A7426@namesys.com>
2003-02-06 22:32   ` Zygo Blaxell [this message]
2003-02-07  6:19     ` link/unlink problem gone? Oleg Drokin
2003-02-09  5:16       ` Zygo Blaxell

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='b1unpa$bmb$1@satsuki.furryterror.org' \
    --to=eazgwmir@umail.furryterror.org \
    --cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.