Re: nfs is stupid ("getfh failed")

[Neil Brown]

On Thursday September 6, [e-mail] wrote:
> Two systems that worked fine for weeks, both running 2.4.[7,8] kernels. The
> server is running 2.4.8 and exporting a reiserfs filesystem via nfs. Or it
> was, anyway. The server was shut down and brought back up (power failure).
> The client was then
> rebooted.
> 
> server# cat /etc/exports
> /export 192.168.1.*(rw,no_root_squash)
> /export/home 192.168.1.*(rw,no_root_squash)

This is not allowed, and makes no sense.
exporting "/export" exports everything below /export that is in the
same filesystem, so exporting "/export/home" as well servers no
purpose and is not allowed (unless /export/home is a separate
filesystem).

Simply remove the second line and your problems should go away.

> client# mount /export
> mount: 192.168.1.1:/export failed, reason given by server: Permission denied
> 
> server# tail /var/log/messages
> Sep  6 09:37:43 gateway rpc.mountd: authenticated mount request from
> 192.168.1.133:933 for /export (/export)
> Sep  6 09:37:43 gateway rpc.mountd: getfh failed: Operation not permitted
> 
> ... so,  rebooting two working systems seems to kill NFS. Any ideas why?
> 
> On a related topic, will Linux ever have a better file-service protocol?

This is an unanswerable question.  The future of Linux is completely
undefined until it happens.

What exactly do you mean by "better" anyway?

NeilBrown
 

> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/