[one-users] Error "Stale NFS file handle"

[Carlos Jiménez]

Hello,

I've configured NFS exports with "fsid=20". So, export options are now:
rw,no_root_squash,fsid=20,sync
After that change I've executed (server side) "exportfs -rav".

The clients were already using NFS v3, so I suppose it is not necessary 
to force it, is it?
Kernel version: 2.4.27-3-386 (server side)
I've shared/exported to the full network 192.168.180.0/24.
The exported directory is /opt/virtual/one and in /opt/virtual it is 
mounted /dev/cciss/c0d0p4 (with default options), which is a 256GB (8GB 
used) partition over a 3 disks RAID5.

We are using an old OS due to the SCSI drivers, not supported on new 
kernel version.


Once added "fsid=20" option, I've tried to create a VM and again the 
same error.

Thu Aug 30 10:03:58 2012 [DiM][I]: New VM state is ACTIVE.
Thu Aug 30 10:03:59 2012 [LCM][I]: New VM state is PROLOG.
Thu Aug 30 10:03:59 2012 [VM][I]: Virtual Machine has no context
Thu Aug 30 10:25:33 2012 [TM][I]: Command execution fail: 
/var/lib/one/remotes/tm/shared/clone 
frontend:/var/lib/one/datastores/1/5c0455eb494fd43b5c7c576e0c642fbe 
Host2:/var/lib/one//datastores/0/32/disk.0 32 1
Thu Aug 30 10:25:33 2012 [TM][I]: clone: Cloning 
../../1/5c0455eb494fd43b5c7c576e0c642fbe in 
Host2:/var/lib/one//datastores/0/32/disk.0
Thu Aug 30 10:25:33 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
Thu Aug 30 10:25:33 2012 [TM][E]: Error copying 
frontend:/var/lib/one/datastores/1/5c0455eb494fd43b5c7c576e0c642fbe to 
Host2:/var/lib/one//datastores/0/32/disk.0
Thu Aug 30 10:25:33 2012 [TM][I]: ExitCode: 1
Thu Aug 30 10:25:33 2012 [TM][E]: Error executing image transfer script: 
Error copying 
frontend:/var/lib/one/datastores/1/5c0455eb494fd43b5c7c576e0c642fbe to 
Host2:/var/lib/one//datastores/0/32/disk.0
Thu Aug 30 10:25:34 2012 [DiM][I]: New VM state is FAILED

Also, I've tried copying a file at a client machine from the NFS Server 
(to /dev/null) and it outputs the same stale error:
[root at host1 1]# cp -v 5c0455eb494fd43b5c7c576e0c642fbe /dev/null
cp: overwrite `/dev/null'? y
`5c0455eb494fd43b5c7c576e0c642fbe' -> `/dev/null'
cp: reading `5c0455eb494fd43b5c7c576e0c642fbe': Stale NFS file handle


Any idea?
Thank you for your help.


Carlos.


On 08/29/2012 08:33 PM, Matthew Patton wrote:
> All of your NFS exports should have 'fsid=<N>' in your parameters.
> I would surmise the NFS client is trying to use NFS v4 and the server 
> doesn't understand it or doesn't handle it gracefully.
> Force the server to only export as NFS v3 or v2 and likewise force 
> your clients to only use v2 or v3.
>
> Doing a loopback copy is pointless. Manually do a copy at a client 
> machine from the NFS server and see how long it takes. (you can copy 
> it to /dev/null if you like).
>
> Once that is confirmed working, then you can see what's going on with 
> NFS v4.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120830/6613a879/attachment-0002.htm>