All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Mario Storti <mstorti@intec.unl.edu.ar>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: NFS synchronization problems on Beowulf cluster
Date: Thu, 01 Jun 2006 13:22:48 -0400	[thread overview]
Message-ID: <447F2268.4090401@redhat.com> (raw)
In-Reply-To: <loom.20060601T175939-701@post.gmane.org>

Mario Storti wrote:

>Peter Staubach <staubach <at> redhat.com> writes:
>
>  
>
>>I see from the `nfsstat' output that this job mix is _very_ heavily write
>>intensive.  I might suspect that this may be contributing to the issue
>>being seen.  The consistency for files is very relaxed when those files
>>are being written to.
>>    
>>
>
>The `nfsstat' results that I sent were cumulative. I learn now that in
>theory we can zero them with `-z', but it seems not to work. Perhaps
>there is some intense traffic when the slaves boot but not at the time
>of making the `experiment'.  At that time the NFS traffic es
>_extremely_ low. We change only a small text file (for reference it's
>my ~/.bashrc) and check if the changes are reflected in the
>nodes. There are no applications running at the nodes. 
>
>  
>

I wouldn't have thought that there would be intense write activity when
the systems are booting.  I could see lots of read activity, but the
stats didn't show that much compared with the number of writes.

>>Are any special mount parameters being used?
>>    
>>
>
>No, we tried vers=2 for forcing version 2, also tried `noac'. Also
>tried `async/sync' at the server side. None had effect on the
>problem. `noac' of course reflected in a lack of efficiency, but the
>problem persists. 
>

I wouldn't think that sync/async would have any effect on this sort
of consistency.  Those options more control when the data/metadata is
actually flushed to stable storage, whether before the server responds
to the specific request or sometime after.

Can you get a raw tethereal capture file which shows the issue?  Perhaps
a capture which includes reading the original contents of the file and
then reading it again after the file is modified on the server or by
another client?  Perhaps from that we can get some clues as to where the
problem might be.

    Thanx...

       ps


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2006-06-01 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 19:23 NFS synchronization problems on Beowulf cluster Mario Storti
2006-06-01 13:58 ` Mario Storti
2006-06-01 14:25   ` Peter Staubach
2006-06-01 14:54     ` Mario Storti
2006-06-01 15:56       ` Peter Staubach
2006-06-01 16:35         ` Mario Storti
2006-06-01 17:22           ` Peter Staubach [this message]
2006-06-01 18:50             ` Mario Storti
2006-06-01 19:03               ` Peter Staubach

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=447F2268.4090401@redhat.com \
    --to=staubach@redhat.com \
    --cc=mstorti@intec.unl.edu.ar \
    --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.