On Fri, May 30, 2008 at 09:14:25AM +0200, Philip Mötteli wrote:
> Hi,
>
>
> Since the update to Mac OS X Server 10.5.3 yesterday, NFS behaves
> strangely.
> I have the following disk configuration:
>
> Filesystem Size Used Avail Capacity Mounted on
> /dev/disk0s3 82G 57G 25G 70% /
> devfs 113k 113k 0B 100% /dev
> fdesc 1.0k 1.0k 0B 100% /dev
> map -hosts 0B 0B 0B 100% /net
> map auto_home 0B 0B 0B 100% /home
> map -fstab 0B 0B 0B 100% /Network/Servers
> map -static 0B 0B 0B 100% /Network/Library
> map -static 0B 0B 0B 100% /Library/MultiMedia
> map -static 0B 0B 0B 100% /Network/Applications
> /dev/disk1s3 391G 337G 54G 87% /Library/MultiMedia
> /dev/disk1s5 108G 103G 5.6G 95% /private/var/backups/TimeMachine
>
>
> I would like to export '/Library/MultiMedia' (/dev/disk1s3), which is, as
> you saw above, a partition on a separate internal disk. So I make the
> simplest export file possible:
>
> #cat /etc/exports
> /Library/MultiMedia
>
>
> And try to give it to the NFSd:
>
> #nfsd update
> May 29 23:37:09 herkules /sbin/nfsd[2969]: Can't export /Library/MultiMedia: Invalid argument (22)
> May 29 23:37:09 herkules /sbin/nfsd[2969]: exports:1: kernel export registration failed
The problem is probably that there are two file systems mounted at /Library/MultiMedia:
> map -static 0B 0B 0B 100% /Library/MultiMedia
> /dev/disk1s3 391G 337G 54G 87% /Library/MultiMedia
The first one is not your disk, but rather an autofs mount trigger.
When the export gets registered, the kernel finds the (first) file
system mounted at the given path and asks that file system for the
NFS file handle of the exported directory.
autofs doesn't know how to support NFS exports, so any attempt to
export it would probably result in an EINVAL (22) error as you saw.
Does the export work if you get rid of the /Library/MultiMedia autofs trigger?
> Though, when I check the configuration everything seems to be ok:
>
> #nfsd checkexports
The nfsd checkexports command is useful for finding errors in and
conflicts between export entries.
Unfortunately, checkexports doesn't do everything that a normal export
would do. It does everything up to the point where the export would
actually get registered in the kernel (where most of the NFS server
functionality lives). This is because registering the export would
make it "live" which is exactly what "checkexports" *doesn't* want to
do. :-)
HTH
--macko
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
