This sounds similiar to the attached e-mail from April.
It looks like it has ben fixed in the source,
http://www.openafs.org/cgi-bin/wdelta/sol10u2-rename-20060703
i.e.
replaced VN_SETPATH with vn_setpath in src/afs/SOLARIS/osi_vnodeops.c
William Setzer wrote:
Under Solaris 10, the 118833-23 kernel patch (-22 is not affected)
removes the 'vn_path' symbol from the generic kernel, and so none
of the precompiled Solaris 10 1.4.1 kernel modules will load.
I grep'd the 1.4.1 source code looking for 'vn_path' and didn't find
it, so I don't know if this problem could bleed over into the 1.4.2
series. I'm posting this as a "heads up" just in case.
William
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
-------- Original Message --------
Subject: Re: OpenAFS and OpenSolaris [was: OpenAFS-1.3.85 on Solaris 10 Problem
with pwd...]
Date: Wed, 05 Apr 2006 13:27:18 -0500
From: Douglas E. Engert <[EMAIL PROTECTED]>
To: Albert S. <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Albert S. wrote:
> Hello,
>
> I am new to OpenAFS and I am not subscribed to the list, which is why
> I am contacting you off-line.
>
> I was experimenting with OpenAFS and OpenSolaris x86, and tried
> installing the client for version 1.4.0, but was getting the following
> errors when loading the module:
>
> genunix: [ID 819705 kern.notice] /kernel/fs/afs: undefined symbol
> genunix: [ID 826211 kern.notice] 'vn_path'
> genunix: [ID 472681 kern.notice] WARNING: mod_load: cannot load module
> '/kernel/fs/afs'
>
> I googled around a little while, and came across a thread titled:
>
> "OpenAFS-1.3.85 on Solaris 10 Problem with pwd after rename of a
> directory"
This has been fixed and was bug number 19412. I am running 1.4.1-rc10
on Solaris 10 on Sparc, have not tried OpenSolaris or SOoaris x86.
I do see that Solaris 10 sys/vnode.h has:
864 /*
865 * This macro should be used instead of calling vn_setpath() directly.
It
866 * optimizes for the common case, where the vnode already has a path.
867 */
868 #define VN_SETPATH(rvp, svp, vp, p, len) { \
869 if (vn_path(vp) == NULL) \
870 vn_setpath((rvp), (svp), (vp), (p), (len)); \
871 }
and http://cvs.opensolaris.org/source/xref/on/uts/common/sys/vnode.h
had vn_setpath, but not VN_SETPATH.
So you could try a patch to the AFS src/afs/SOLARIS/osi_vnodeops.c
with something like:
#ifdef VN_SETPATH
VN_SETPATH(afs_globalVp, pvp, vp, aname2, strlen(aname2));
#else
vn_setpath(afs_globalVp, pvp, vp, aname2, strlen(aname2));
#endif
And if it works send it to openafs-bugs
>
> and I don't know if the problems that were discussed related to the
> introduction of 'v_path' (note the spelling difference) in Solaris 10
> were related to the problems that I am having. I worked my way
> backwards, and I am able to get the client for 1.3.81 to work,
> seemingly without any problems.
>
> Are there developers actively working on Solaris 10 or OpenSolaris? If
> so, are they aware of this problem?
>
Solaris 10 I would say yes, and we will surely get involved if OpenAFS does
not work as we have a large commitment to Solaris. I don't know about
OpenSolaris.
> I also wanted to experiment with the namei fileserver and ZFS vice
> partitions. I have compiled a few versions of the fileserver between
> 1.3.81 and 1.4.0 with namei support, but it does not see the ZFS vice
> partitions. Theoretically, shouldn't this work? Do any of you know if
> anyone has tried this?
>
> Thanks,
> Albert
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's
> FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
--
Douglas E. Engert <[EMAIL PROTECTED]>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
--
Douglas E. Engert <[EMAIL PROTECTED]>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
