From: "William A. (Andy) Adamson" <androsadamson@gmail.com>
To: redshield88888 <redshield88888@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: How does the metadata-server synchronizes with data-servers ?
Date: Mon, 24 May 2010 09:52:48 -0400 [thread overview]
Message-ID: <AANLkTimUM1W5xIF3pTYDTxy4eNEC5MLcCpgTncQobAFQ@mail.gmail.com> (raw)
In-Reply-To: <4BF854D4.5090500@gmail.com>
2010/5/22 redshield88888 <redshield88888@gmail.com>:
> Hi, all.
>
> I've succeeded to install pNFS-enabled kernel. But I wonder that how
> does pNFS behaviour.
> Especially, about synchronizations between the MetaDataServer and
> DataServers.
pNFS does not specify any MDS <-> DS protocol.
> I'd read a paper of the Calsoft's. This paper said like "There is
> heartbeats betweenthe MetaDataServer and DataServers".
> http://www.calsoftinc.com/download_pdf/White%20Papers%20-%20pnfs.pdf
>
> When will this heartbeat be started ? The instruction below is not describe
> about this, but the heartbeat will works, w'not this ?
> http://wiki.linux-nfs.org/wiki/index.php/PNFS_Setup_Instructions
These instructions need to be clarified. There are two file layout
server implementations. One is based on GFS2 where GFS2 nodes can be
an MDS, a DS or both an MDS/DS. GFS2 has it's own heartbeat and such
between GFS2 nodes.
The other file layout implementation is spNFS, which is not a
full-blown file system in that there is limited communication between
the MDS and the DS. There is no heart beat..
Updating the pNFS setup page is on our todo list...
-->Andy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-05-24 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 22:04 How does the metadata-server synchronizes with data-servers ? redshield88888
2010-05-24 13:52 ` William A. (Andy) Adamson [this message]
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=AANLkTimUM1W5xIF3pTYDTxy4eNEC5MLcCpgTncQobAFQ@mail.gmail.com \
--to=androsadamson@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=redshield88888@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).