All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Carlos Jiménez" <cjimenez@eneotecnologia.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Stale NFS file handle - persistent error
Date: Wed, 29 Aug 2012 13:11:23 -0400	[thread overview]
Message-ID: <20120829171122.GA9983@fieldses.org> (raw)
In-Reply-To: <503E13BF.6010304@eneotecnologia.com>

On Wed, Aug 29, 2012 at 03:06:07PM +0200, Carlos Jiménez wrote:
> I have a computer acting as an NFS Server running a Debian based
> distro

Could you be more specific?  What kernel version exactly, and what
filesystem are you exporting, and what are the export options?

What version of NFS are you using?

> and several hosts running CentOS 6.2 acting as NFS clients
> (for a virtualization environment). Every time more often "Stale NFS
> file handle" errors appear when trying to copy a file from one
> directory to another (both in the nfs shared directory).

I assume you're not doing anything else with either file or directory at
the same time?  (E.g., not deleting or renaming the file while it's
being copied?)

--b.

> In the server side there are no related information in the logs, but
> this is the output of one of the nfs clients:
> 
> Wed Aug 29 11:52:57 2012 [TM][E]: clone: Command "cd
> /var/lib/one/datastores/0/32; cp -r
> ../../1/5c0455eb494fd43b5c7c576e0c642fbe
> /var/lib/one/datastores/0/32/disk.0" failed: cp: reading
> `../../1/5c0455eb494fd43b5c7c576e0c642fbe': Stale NFS file handle
> 
> I've checked that path and filenames are correct. The file itself is
> a 300MG sized and the error appears aprox. 30 minutes after the
> start of the copy, so I guess that it doesn't finish the file copy.
> I usually tried unmounting and remounting the shared directory. In
> fact, initially it was enough and it was possible to fully copy the
> file (after aprox. 30 minutes), moreover because the error took
> place from time to time. But now, the problem persists after doing
> it (even after rebooting the clients).
> Additionally, I've tried doing the same operation (to copy the same
> file from a directory to another) locally in the NFS Server and it
> takes just a minute (aprox.).
> 
> Could you give me advice on troubleshooting it?
> 
> 
> Thanks in advance.
> 
> Carlos.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-29 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <503E131F.2040904@eneotecnologia.com>
2012-08-29 13:06 ` Stale NFS file handle - persistent error Carlos Jiménez
2012-08-29 17:11   ` J. Bruce Fields [this message]
2012-08-30  6:45     ` Carlos Jiménez
2012-08-30  9:17       ` Carlos Jiménez
2012-08-30 16:02       ` Bryan Schumaker
2012-08-30 18:59         ` J. Bruce Fields
2012-08-31  6:09           ` Carlos Jiménez

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=20120829171122.GA9983@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=cjimenez@eneotecnologia.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.