From: Benny Halevy <bhalevy@panasas.com>
To: quanli gui <gqlxj1987@gmail.com>
Cc: linux-pnfs <linux-nfs@vger.kernel.org>
Subject: Re: [pnfs]ds ip
Date: Tue, 13 Jul 2010 11:32:01 +0300 [thread overview]
Message-ID: <4C3C2481.1090708@panasas.com> (raw)
In-Reply-To: <AANLkTilJTogMkslFT-bGoOJYgGSznHnpi75e6IeCuWzC-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Jul. 13, 2010, 5:05 +0300, quanli gui <gqlxj1987@gmail.com> wrote:
> I use
> #define dprintk printk
You don't have to modify the kernel to see the debug prints...
You can turn the debug prints on and off in run time
by writing the numeric bitmask (in ASCII) into /proc/sys/sunrpc/nfs_debug
for example:
# echo 32767 > /proc/sys/sunrpc/nfs_debug
> to show some messages in the pnfs process. In the pnfs process, the
> client would use some functions in nfs4filelayoutdev.c to connect with
> ds. But from the printk messages, I found that the functions that
> connect to the ds printk the ip message, which is belong to the mds. Do
> the client only connect to the mds? Do the mds become the storage server
> which connect to the client? This conficts the pnfs architecture.Please
> give me some answers.
The client should communicate with the DS for I/O operations.
If the MSD has dual function, both as a DS and a MDS, the DS ip address
may be the same as the MDS's.
Can you give an example of a particular message you're worried about?
What do you have running on the server side?
Benny
next parent reply other threads:[~2010-07-13 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTilJTogMkslFT-bGoOJYgGSznHnpi75e6IeCuWzC@mail.gmail.com>
[not found] ` <AANLkTilJTogMkslFT-bGoOJYgGSznHnpi75e6IeCuWzC-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-13 8:32 ` Benny Halevy [this message]
[not found] ` <AANLkTilyAgrY6Sa07ef1QmUhV1OkeKSMug45LwBEeCMg@mail.gmail.com>
[not found] ` <AANLkTilyAgrY6Sa07ef1QmUhV1OkeKSMug45LwBEeCMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-19 7:38 ` [pnfs]ds ip Benny Halevy
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=4C3C2481.1090708@panasas.com \
--to=bhalevy@panasas.com \
--cc=gqlxj1987@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 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.