Subject: NFS file handle stability, was Re: exporting -ro nfs
To: None <tech-security@netbsd.org>
From: Travis H. <travis+ml-tech-security-netbsd@subspacefield.org>
List: tech-security
Date: 02/27/2007 01:41:55
--MmQIYbZiCoQ2kDro
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 28, 2007 at 02:16:53PM -0500, rick@snowhite.cis.uoguelph.ca wro=
te:
> I'm not sure how you are going to implement "different mapping"? Remember
> that file handles are T stable, which means they refer to a file even
> long after the file is deleted, must work across server reboots, etc.

That's what I thought, but every time I access a file handle from my
[Linux] NFS server after it has crashed, I get "stale file handle" and
can't do anything with it.  The client ends up needing a reboot.  So
much for NFS being stateless, at least with Linux implementations.

--=20
Good code works.  Great code can't fail. -><-
<URL:http://www.subspacefield.org/~travis/>
For a good time on my UBE blacklist, email john@subspacefield.org.

--MmQIYbZiCoQ2kDro
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (OpenBSD)

iQIVAwUBRePgw2QVZZEDJt9HAQIHMQ/9HMwUrnFJ3AOoojvLKF2ZGYRrWRky6sgB
esDD4Y5Jg3r7P4IU9EmaQsMHIpCheWvldHAg+v7AGbfgJDqned/QgMn1EGGnQdiX
MNoYdVntvbKWYj5WFYQFn4sohSy+JVWjEKfueO8PThvoaIJo7EGKoEVzdsYnFDvq
XXJzkwuUqqPnY//MYJRM5nMkaFJSQ5sTMgaHtn12mMMraUOegPVyyDHTjmOb9EK6
HNkrttJ8WTlpJyA521+rq4VVL2oX7dceZi0NKB82RNkEAJtMuuSdw9panE/rSAya
7GmTRkeUI9Ajo+xjGJFPWvt7a8qSa0+NWlo3lqQrRkFd7eHRN6IYMd/yX1sNiLkF
TA5IhM0wDHSQW1k41HpGRJY7KqA73krip6HGZGMtMQ9w3z7nDtIUJGPquvUc5/9w
Mlg9isd6Aj/SKkhawnAG5bpG6qiStolMPZCx1HZA4gD8JKybUKAVYuYJm7YxJofU
WVcvM4FB0eWspMDlzjWz2LCUzPtirq6pVloHwkLRpFINeRTPQ6ALK/Ii0L7of7U8
CU+y7jmCx9VvaEk8DwLIjo1PFIOW4mMvo72YUAQTRwUZ+7C4DyOFJyQdLwI+97+q
MWL/RyjMgRqmlDoM/+89u8nx1upL9f/RkplxYZvjOT0ukhY8ldCRLSl7Qd7rnca+
+VHwNle5mJE=
=Rs1U
-----END PGP SIGNATURE-----

--MmQIYbZiCoQ2kDro--