From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Cc: gam3@acm.org
Subject: Re: Problems with NFS exports
Date: Wed, 07 Aug 2002 11:25:33 +0200 [thread overview]
Message-ID: <87k7n3t3zm.fsf@deneb.enyo.de> (raw)
In-Reply-To: <87eldchtr2.fsf@deneb.enyo.de> (Florian Weimer's message of "Tue, 06 Aug 2002 18:00:06 +0200")
Florian Weimer <fw@deneb.enyo.de> writes:
> I'm seeing weired errors with nfsctl():
>
> This works:
>
> nfsservctl(NFSCTL_EXPORT, "deneb.enyo.de", "/mnt/storage/2/backup/deneb/tmp", makedev(3, 66), ino 167772288, uid 65534, gid 65534) = 0
>
> But a subsequent call fails:
>
> nfsservctl(NFSCTL_EXPORT, "deneb.enyo.de", "/mnt/storage/2/backup/deneb", makedev(3, 66), ino 150995072, uid 65534, gid 65534) = -1 EINVAL (Invalid argument)
>
> I don't understand what makes the difference (the inode values are
> correct). This is kernel 2.4.18 with XFS support, and the directory
> resides on an XFS file system.
>
> Any ideas?
(Full quote because of additional recipeint.)
It appears that a directory tree can only be exported once. Is this
intentional? If yes, the following patch should be applied (to
linux/fs/nfsd/export.c), so that the return value is more meaningful:
--- export.c 2002/08/07 09:22:11 1.1
+++ export.c 2002/08/07 09:22:28
@@ -219,6 +219,7 @@
goto finish;
}
+ err = -EBUSY;
if ((parent = exp_child(clp, dev, nd.dentry)) != NULL) {
dprintk("exp_export: export not valid (Rule 3).\n");
goto finish;
After this change, the userspace tools can issue are more meaningful
error message for this case.
next prev parent reply other threads:[~2002-08-07 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:49 Problems with NFS exports Florian Weimer
2002-08-07 9:25 ` Florian Weimer [this message]
2002-08-07 10:40 ` Neil Brown
2002-08-07 11:13 ` Florian Weimer
2002-08-07 11:18 ` Neil Brown
2002-08-07 11:51 ` Florian Weimer
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=87k7n3t3zm.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gam3@acm.org \
--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