All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: "Martin Schuster (IFKL IT OS DSM CD)"
	<Martin.Schuster1-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [NFS] re-exporting NFS-mounted dir over NFS
Date: Wed, 04 Jun 2008 10:46:11 -0400	[thread overview]
Message-ID: <4846AAB3.9070005@redhat.com> (raw)
In-Reply-To: <4846A272.8040206-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org>

Martin Schuster (IFKL IT OS DSM CD) wrote:
> I am in the process of setting up an "NFS-proxy", a machine which
> mounts directories from an NetApp-filer using NFS3, and should re-export
> them using NFS4 (with Kerberos).
>
> But apparently nfsd doesn't support re-exporting NFS-mounted dirs:
> # mount | grep home
> netapp.example.com:/vol/home/schumar on /srv/nfs4/home/schumar type nfs
> # cat /etc/exports
> /srv/nfs4/home/schumar  gss/krb5(rw,sync,fsid=0,secure,no_subtree_check)
> # exportfs -r
> exportfs: Warning: /srv/nfs4/home/schumar does not support NFS export.
>
> I traced this back to linux-2.6.25.1/fs/nfsd/export.c, where it says, starting
> in line 386:
>         if (!inode->i_sb->s_export_op ||
>             !inode->i_sb->s_export_op->fh_to_dentry) {
>                 dprintk("exp_export: export of invalid fs type.\n");
>                 return -EINVAL;
>         }
>
> (and a quick look in fs/nfs/super.c confirmed that the nfs-client never
> sets an export_op)
>
> Is there a technical reason for this (i.e. is it simply theoretically
> impossible to re-export an NFS-mount), or is my use-case so strange that
> nobody has ever needed this until now, and thus it just wasn't coded?
> Or am I just stupid/blind? (wouldn't be the first time :)
>
> Thanks in advance,
>   
Is the real goal to be able to export the files using krb5
authentication or the use of NFSv4?

If the former, then why not just export the files from the
NetApp using Kerberos?

If the latter, then I suspect that it won't provide much, if
any, benefit.  It would still be limited to the NFSv3 semantics
of the file system.

    Thanx...

       ps

  parent reply	other threads:[~2008-06-04 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 14:10 [NFS] re-exporting NFS-mounted dir over NFS Martin Schuster (IFKL IT OS DSM CD)
     [not found] ` <4846A272.8040206-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org>
2008-06-04 14:46   ` Peter Staubach [this message]
2008-06-05  6:26     ` Martin Schuster (IFKL IT OS DSM CD)
     [not found]       ` <4847871A.5000206-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org>
2008-06-05 11:47         ` Peter Staubach
2008-06-05 18:33           ` J. Bruce Fields
2008-06-05 16:08         ` Chuck Lever
2008-06-05 18:30   ` J. Bruce Fields

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=4846AAB3.9070005@redhat.com \
    --to=staubach@redhat.com \
    --cc=Martin.Schuster1-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.