From: Simone Carbonara <simone-2dnJtoj8yUAi5CQI31g/s0B+6BGkLq7r@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Strange NFS behaviour
Date: Fri, 23 May 2008 11:41:55 +0200 [thread overview]
Message-ID: <g163h5$3mu$3@ger.gmane.org> (raw)
Hello,
i'm experiencing on debian etch the following behaviour with NFS.
I have 1 backend running linux debian sarge that exports via NFS a SVN
working copy to a couple of frontend (debian etch) that read the
contents of the exported NFS share called /WEB-2 (under drbd ) and
publish it via apache.
Sometimes when i update my working copy on my backend i don't see the
changes on all the frontends as follows the output on ls on the frontends.
FE-01:~# ls -alio /WEB-2/sites/http/pilot/frontend/contenuto_lista_nozze.php
17237334 -rw-r----- 0 vapache 3387 2008-05-16 11:10
/WEB-2/sites/http/pilot/frontend/contenuto_lista_nozze.php
FE-02:~# ls -alio /WEB-2/sites/http/pilot/frontend/contenuto_lista_nozze.php
17237564 -rw-r--r-- 1 vapache 3801 2008-05-23 11:09
/WEB-2/sites/http/pilot/frontend/contenuto_lista_nozze.php
If i remount the /WEB-1 share on the frontend the changes are seen and
updated correctly on all frontends but it's clear that this behaviour is
not accetable when writing codes that needs to be updated directly on
production.
The exportfs flag options on the exported fs on the Backend are as follows
rw,all_squash,anonuid=4001,anongid=555,no_subtree_check,sync.
Someone could address me in any troubleshooting steps on this issue?
Best Regards,
Simone Carbonara
next reply other threads:[~2008-05-23 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 9:41 Simone Carbonara [this message]
2008-05-23 17:22 ` Strange NFS behaviour david m. richter
2008-05-25 7:12 ` Simone Carbonara
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='g163h5$3mu$3@ger.gmane.org' \
--to=simone-2dnjtoj8yuai5cqi31g/s0b+6bgklq7r@public.gmane.org \
--cc=linux-nfs@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 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.