From: Shehjar Tikoo <shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Errors during a simple mount storm test
Date: Fri, 05 Feb 2010 02:12:51 +0530 [thread overview]
Message-ID: <4B6B314B.4050408@gluster.com> (raw)
In-Reply-To: <1265315573.3317.50.camel@localhost>
Trond Myklebust wrote:
> On Fri, 2010-02-05 at 01:45 +0530, Shehjar Tikoo wrote:
>> Hi All
>>
>> The shell command below is probably not applicable to
>> all real world setups but I wanted to check it out nonetheless.
>> The problem is with the following command that is supposed
>> run a mount-umount loop:
>>
>> $ while [ true ]; do echo sending; mount localhost:/test -o
>> noacl,nolock,tcp,mountproto=tcp /mnt;umount /mnt; done
>>
>> For the first hundred iterations, it works fine but then starts
>> spewing errors with the mount command failing. For eg.
>> the output looks like below:
>>
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> sending
>> mount.nfs: mount system call failed
>> umount: /mnt: not mounted
>> sending
>> mount.nfs: mount system call failed
>> umount: /mnt: not mounted
>> sending
>> mount.nfs: mount system call failed
>> umount: /mnt: not mounted
>> sending
>> mount.nfs: mount system call failed
>> umount: /mnt: not mounted
>>
>> Any ideas why the mount sequence stops abruptly?
>> There dont seem to be any relevant messages in the
>> dmesg output either.
>>
>> The client and server are on the same machine:
>> Linux indus 2.6.31-17-generic Ubuntu SMP x86_64 GNU/Linux
>>
>> I have verified through wireshark that the server is not
>> receiving any mount requests once the mount command start
>> failing. Instead there are only successful GETPORT requests
>> for the MOUNTv3 program.
>
> "netstat -t" will probably show you that all your free ports in the
> range 0-1023 are now in the TIME_WAIT state. This again means that you
> have to wait a couple of minutes for the TIME_WAITs to expire before you
> can try again.
>
> So basically, it is a case of your test being flawed.
Thanks!
I'll to resort to using noresvport in that case.
-Shehjar
>
> Trond
>
prev parent reply other threads:[~2010-02-04 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:15 Errors during a simple mount storm test Shehjar Tikoo
[not found] ` <4B6B2AE5.1070007-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org>
2010-02-04 20:32 ` Trond Myklebust
2010-02-04 20:42 ` Shehjar Tikoo [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=4B6B314B.4050408@gluster.com \
--to=shehjart-+fkpdpinhgjbdgjk7y7tuq@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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