Ty,
The error code -1073741826 is "no such file or directory". I got that info
from "/opt/orangefs/bin/pvfs2-perror 1073741826" on the server.

Now obviously you shouldn't get that error for the / directory.

You can check Windows Event Log for additional information.

Are you able to access the file system with a Linux client? Like doing
"/opt/orangefs/bin/pvfs2-ls /mnt/orangefs"? (Substituting /mnt/orangefs for
what you have set up in /etc/pvfs2tab.)

For server-side logging, have you changed the EventLogging option in your
orangefs.conf file? I recommend setting it to "server,getattr" to start
with.

Thanks,
Sam Sampson
Omnibond OrangeFS Team


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ty
Christensen
Sent: Wednesday, June 24, 2015 11:33 PM
To: [email protected]
Subject: [Pvfs2-users] New FS and Windows client problem

Hello,

I've been tinkering with OrangeFS 2.9.1 for a few weeks now.  I have a 6
node filesystem running, or so I think.  I'm trying to get a Windows client
to connect to it.  Upon starting the OrangeFS service, I get this debug
information in the client-side log:

[D 20:05:42.523000] Entering DokanMain
[D 20:05:46.018000] OpenDirectory: \
[D 20:05:46.018000]    get_credential:  context: 0
[D 20:05:46.018000]    get_requestor_credential: enter
[D 20:05:46.018000]    get_requestor_credential: requestor: chuck
[D 20:05:46.018000]    get_cache_user: hit for chuck (0:0)
[D 20:05:46.018000]    get_requestor_credential: exit
[D 20:05:46.018000]    get_credential:  requestor credential (0:0)
[D 20:05:46.018000]    get_credential:  exit
[D 20:05:46.018000]    resolved path: /
[D 20:05:46.033000]    fs_getattr returns: -1073741826
[D 20:05:46.033000] OpenDirectory exit: -2 (-1073741826)

I am unable to access the mapped drive that OrangeFS maps to, although it
does show up in Explorer.  I don't get any logging on the server side.  I'm
only using list security, and I'm mapping the Windows user "chuck" to the
root user on the storage nodes.  Security is completely unnecessary in this
case, so I'm trying to keep the entire config as simple as possible.

Does anyone know right off why the Windows client would throw this message
and refuse to access the OrangeFS mapped drive?  I would guess it's a
permissions issue of the directory on the storage node side, but then I'd
think I'd at least get a log line indicating that as the problem.  Let me
know if you need further information.

Thanks,
Ty


_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to