public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Timur Aydin <ta@taydin.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] configuring NFS server to handle client reboots
Date: Sun, 30 Jun 2013 20:16:53 +0300	[thread overview]
Message-ID: <51D06805.8080509@taydin.org> (raw)
In-Reply-To: <51D0669D.7070000@taydin.org>

On 06/30/13 20:10, Timur Aydin wrote:
> Here is the mount command:
> 
> mount -o nolock,tcp 10.2.2.254:/romfs_2011R1 /mnt
> 

BTW, when I use UDP instead of TCP, then the mount works after repeated
reboots. But I would rather use TCP, because based on past experiments I
did, TCP mounted NFS shares have a higher bandwidth.

Also, when using TCP, if I restart the NFS server on the gentoo host,

/etc/init.d/nfs restart

Then I can mount the NFS share on the Blackfin repeatedly.

This all tells me that the NFS server is preventing subsequent TCP
mounts unless the existing mount is unmounted first.

-- 
Timur


  reply	other threads:[~2013-06-30 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 17:10 [gentoo-user] configuring NFS server to handle client reboots Timur Aydin
2013-06-30 17:16 ` Timur Aydin [this message]
2013-06-30 17:26 ` Timur Aydin
2013-07-01  2:09 ` Walter Dnes
2013-07-01 10:07   ` Timur Aydin

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=51D06805.8080509@taydin.org \
    --to=ta@taydin.org \
    --cc=gentoo-user@lists.gentoo.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