From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: "Margulies, Adam" <amarguli@hotjobs.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: nfs is stupid ("getfh failed") -- exporting a mountpoint?
Date: 06 Sep 2001 19:34:12 -0400 [thread overview]
Message-ID: <999819252.2266.1.camel@gromit.house> (raw)
In-Reply-To: <A6818BDFB20BD5118B5C00B0D049C021526740@element.ny.genx.net>
In-Reply-To: <A6818BDFB20BD5118B5C00B0D049C021526740@element.ny.genx.net>
Is there a problem with exporting a mount point? It seems that, as long
as I'm not trying to export "/export", which is where the resierfs
filesystem is mounted, things are working okay. I was exporting /export
and /export/home before, now I'm exporting /export/home and
/export/files, with pretty much everything in /export moved into
/export/files (except for /export/home).
-M
On 06 Sep 2001 11:28:35 -0400, Margulies, Adam wrote:
> I have had similar problems in the past. Everytime I've rebooted my main nfs
> server I've had to reboot my clients of that nfs for things to work
> correctly. If a client remained up and running, I'd get strange errors from
> the server.
>
> Reiserfs has had some known nfs problems (with known patches) for some time.
> It all seems to have resolved itself with the 2.4.9+ kernels.
>
> -----Original Message-----
> From: Michael Rothwell [mailto:rothwell@holly-springs.nc.us]
> Sent: Thursday, September 06, 2001 10:36 AM
> To: linux-kernel@vger.kernel.org
> Subject: nfs is stupid ("getfh failed")
>
>
> 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)
>
> 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?
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
> ----------------------------------------------------------------------------
> -------------------------------------------------------
> Private and Confidential
> This electronic mail may contain confidential information that is intended
> for the use of the addressee only or others authorized to receive it. If you
> are not the intended recipient, you are hereby notified that any disclosure,
> copying, distribution or taking action in reliance on the contents of the
> information is strictly prohibited. If you receive this mail in error,
> please delete it from your system immediately and notify HotJobs.com, Ltd.
> - support@hotjobs.com
parent reply other threads:[~2001-09-06 23:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <A6818BDFB20BD5118B5C00B0D049C021526740@element.ny.genx.net>]
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=999819252.2266.1.camel@gromit.house \
--to=rothwell@holly-springs.nc.us \
--cc=amarguli@hotjobs.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®