From: "Tradebit Service" <info@tradebit.com>
To: <nfs@lists.sourceforge.net>
Subject: blocked remote subdirectories
Date: Thu, 8 Dec 2005 03:29:28 +0100 [thread overview]
Message-ID: <E1EkBVL-0003Ee-9s@mail.sourceforge.net> (raw)
hi everybody,
for a few days now i run a new setup
with NFS on RHEL4 (kmountd nfs-utils 1.0.6) and
from our storage I serve a few hundred thousand
files of all sizes to 3 other servers.
now, in these (around 14) days, I had 5 incidents of
blocked subdirectories on the server from different clients.
2 times the directory "came back" after a few minutes
(have seen that mail too late) and in the 3 other cases,
it did not (maybe I was too fast).
for the time the dir is blocked, the failure looks
like a rights mismanagement, but nothing changed it just
denies access for minutes/hours.
the directories were deep in the dir tree, but random as
it seems.
does anyone know, how to prevent that in the future?
what could be the cause of these voodoo incidents?
any help appreciated,
thx,
Ralf Schwoebel
http://www.tradebit.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-12-08 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:29 Tradebit Service [this message]
2005-12-08 5:19 ` blocked remote subdirectories Neil Brown
2005-12-08 11:51 ` Tradebit Service
2005-12-08 11:26 ` Tradebit Service
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=E1EkBVL-0003Ee-9s@mail.sourceforge.net \
--to=info@tradebit.com \
--cc=nfs@lists.sourceforge.net \
/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.