<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
I've configured NFS exports with "fsid=20". So, export options are
now:<br>
rw,no_root_squash,fsid=20,sync<br>
After that change I've executed (server side) "exportfs -rav".<br>
<br>
The clients were already using NFS v3, so I suppose it is not
necessary to force it, is it?<br>
Kernel version: 2.4.27-3-386 (server side)<br>
I've shared/exported to the full network 192.168.180.0/24.<br>
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.<br>
<br>
We are using an old OS due to the SCSI drivers, not supported on new
kernel version.<br>
<br>
<br>
Once added "fsid=20" option, I've tried to create a VM and again the
same error.<br>
<br>
<font face="Helvetica, Arial, sans-serif"><small>Thu Aug 30 10:03:58
2012 [DiM][I]: New VM state is ACTIVE.<br>
Thu Aug 30 10:03:59 2012 [LCM][I]: New VM state is PROLOG.<br>
Thu Aug 30 10:03:59 2012 [VM][I]: Virtual Machine has no context<br>
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<br>
Thu Aug 30 10:25:33 2012 [TM][I]: clone: Cloning
../../1/5c0455eb494fd43b5c7c576e0c642fbe in
Host2:/var/lib/one//datastores/0/32/disk.0<br>
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<br>
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<br>
Thu Aug 30 10:25:33 2012 [TM][I]: ExitCode: 1<br>
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<br>
Thu Aug 30 10:25:34 2012 [DiM][I]: New VM state is FAILED</small></font><br>
<br>
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:<br>
<font face="Helvetica, Arial, sans-serif"><small>[root@host1 1]# cp
-v 5c0455eb494fd43b5c7c576e0c642fbe /dev/null <br>
cp: overwrite `/dev/null'? y<br>
`5c0455eb494fd43b5c7c576e0c642fbe' -> `/dev/null'<br>
cp: reading `5c0455eb494fd43b5c7c576e0c642fbe': Stale NFS file
handle</small></font><br>
<br>
<br>
Any idea?<br>
Thank you for your help.<br>
<br>
<br>
Carlos.<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/29/2012 08:33 PM, Matthew Patton
wrote:<br>
</div>
<blockquote cite="mid:op.wjte5xzvmtfvvt@mpatton-pc.inforelay.net"
type="cite">All of your NFS exports should have 'fsid=<N>'
in your parameters.
<br>
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.
<br>
Force the server to only export as NFS v3 or v2 and likewise force
your clients to only use v2 or v3.
<br>
<br>
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).
<br>
<br>
Once that is confirmed working, then you can see what's going on
with NFS v4.
<br>
<br>
</blockquote>
<br>
</body>
</html>