From: redshield88888 <redshield88888@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: I've succeeded !!! thanks
Date: Tue, 25 May 2010 05:43:07 +0000 (UTC) [thread overview]
Message-ID: <loom.20100525T073755-468@post.gmane.org> (raw)
In-Reply-To: 4BFB4A51.8040405@panasas.com
Thanks Benny
I've succeeded to test the pNFS-behaviour !
I can write a file to a DS from a client through the MDS.
Amasing result now and I'll test cases that have massive number of DSs.
Thanks Benny. Your advertisements had worked very fine!
Regards.
next prev parent reply other threads:[~2010-05-25 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 2:06 Where is the spnfsd in ? redshield88888
2010-05-25 3:56 ` Benny Halevy
2010-05-25 4:29 ` redshield88888
2010-05-25 5:43 ` redshield88888 [this message]
[not found] ` <loom.20100525T073755-468-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-05-25 6:19 ` I've succeeded !!! thanks Benny Halevy
2010-05-25 8:27 ` redshield88888
2010-05-25 8:38 ` An empty file can create but I can't r/w from a pNFS-client with Fsync error. Why? redshield88888
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=loom.20100525T073755-468@post.gmane.org \
--to=redshield88888@gmail.com \
--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 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).