From: AMIT SAHRAWAT <a.sahrawat@samsung.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: Re: Re: [Problem]NFS Server – Um?ount results in Device Busy.
Date: Fri, 11 May 2012 08:37:33 +0000 (GMT) [thread overview]
Message-ID: <373541.55191336725451746.JavaMail.weblogic@epml01> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252, Size: 1768 bytes --]
Hi Bruce,
Sorry it was the mail composer - I did not check mark the plain text option.
We need an opinion.
We will be using around 15 NFS client mounted - with one NFS Server. We are try to make out how many NFSD should we start at the NFS Server.
It all depends upon the load - these 15 NFS clients are going to generate. But is there any default number - we should use to start with? like 1 per NFS client mount?
Please share your advise on this.
Thanks & Regards,
Amit Sahrawat
------- Original Message -------
Sender : J. Bruce Fields<bfields@fieldses.org>
Date : May 10, 2012 17:46 (GMT+05:30)
Title : Re: Re: [Problem]NFS Server Um?ount results in Device Busy.
On Thu, May 10, 2012 at 11:54:43AM +0000, AMIT SAHRAWAT wrote:
>
>
Hi Bruce,
>
>
Thanks for instant reply.
Could you turn off html formatting on your mail?
>
The option you mentioned is working. 'exportfs -f'
>
Actually it is not mentioned anywhere - even when checked for options:
>
#> exportfs -h
exportfs: invalid option -- 'h'
usage: exportfs [-aruv] [host:/path]
Sorry, it looks like the help test could be improved! Patches
welcomed....
It is documented in the exportfs man page.
>
But - when tried to give - '-f' option it is working.
>
Then on checking the code for exportfs - got to know the working of '-f' option.
>
I think it should work. I will check with a number of scenario - to check there is no blockage for other mount points - at the time 'exportfs -f' is being run. Please reply if it wont :)
If no clients are using the export, it should work.
--b.
Thanks & Regards,
Amit Sahrawatÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
reply other threads:[~2012-05-11 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=373541.55191336725451746.JavaMail.weblogic@epml01 \
--to=a.sahrawat@samsung.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=namjae.jeon@samsung.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