08-03-2007
Thanks guys.
I thought that was the case.
Also, Sharity looks interesting but it still relies on nfs (at least locally). Plus, the website states there maybe issues in stale NFS file handlers being reported when it attempts to handle locking implementation.
I guess I should just rely on sharing the dirs via NFS and CIFS on the solaris system.
10 More Discussions You Might Find Interesting
1. AIX
Im trying to share a directory with cifs my aix box with a windows server.
but when I try to mount
mount -v cifs -n 172.19.90.240/suc_user/tommy /directory /directory1/directory1
I got this error
There was an error connecting the share or the server.
Make sure the lsdev command shows that... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
2. AIX
Dear All,
I mounted a windows share on AIX 5.3. with cifs.
The write on it is much slower than from other windows clients.
Could you help me with any tricks to speed the writing process?
Thanks,
Zoltán Patalenszki (0 Replies)
Discussion started by: zoltanp
0 Replies
3. HP-UX
Share ServerA
==== The Samba server is running on Samba version 3.0.22 based HP CIFS Server A.02.03.04
/opt/cifsclient/sbin/cifsclientd version: HP CIFS Client - Version A.02.02.02 smb file:
My previous casw was thew user wasn't able to write to the share from Windows... (1 Reply)
Discussion started by: lamoul
1 Replies
4. AIX
Dear Experts,
Im facing a unique situation. We got a windows server folder cifs mounted on my AIX server. Before restarting the win server I tried unmounting the cifs mount. It got hanged and win server was restarted however.
Now Im trying to mount the same. It prompts for password... (3 Replies)
Discussion started by: jayadeava
3 Replies
5. Solaris
Hello guys,
as of recently I'm unable to connect to one of my CIFS shares and I've no clue why that may be. As you can see in the first attachment a connection attempt to tony prompts for user credentials but when I try to connect to Videos it claims not being able to find the resource which is... (1 Reply)
Discussion started by: Tony~
1 Replies
6. AIX
I have an AIX box that mounts a Windows share across subnets. When I try to copy a 100 MB file to it, it copies around 2 MB/s. If I copy to another Windows share on the same subnet it copies around 12 MB/s. All I have is gigabit networks so I would expect it to go well over 12 MB/s, which is the... (8 Replies)
Discussion started by: kah00na
8 Replies
7. Red Hat
Hi Guys,
need help here.
i have windows server that share a folder C:/ABCDE
i configure samba client in Linux server as /EDCBA and it working fine.
then i want to share this /EDCBA to another Linux server using NFS.
in the /etc/exportfs i have put
/EDCBA - *(rw,no_root_squash)
... (1 Reply)
Discussion started by: prossits
1 Replies
8. AIX
Hi Guys,
need help here.
i have windows server that share a folder C:/ABCDE
i configure samba client in AIX server as /EDCBA and it working fine.
then i want to share this /EDCBA to another AIX server using NFS.
in the /etc/exportfs i have put
/EDCBA... (1 Reply)
Discussion started by: prossits
1 Replies
9. AIX
Hi All,
I was trying to setup a file share between AIX and widnows servers. I have installed cifs filesets on my AIX LPAR. but when i was trying to mount the share on AIX , got the below errors.
There was an error connecting the share or the server.
Make sure the lsdev command shows that... (3 Replies)
Discussion started by: System Admin 77
3 Replies
10. Windows & DOS: Issues & Discussions
Hi All
Actually I have NAS Storage and Suddenly I got problem
Unable to access the CIFS share folder on windows host, however the IP is pinging and the share is accessible via share name.
The share can be accessed via share name only on Windows higher Windows Versions.
Any help guys (4 Replies)
Discussion started by: Abu_SM
4 Replies
nfs(7) Miscellaneous Information Manual nfs(7)
NAME
nfs, NFS - network file system
DESCRIPTION
The Network File System (NFS) allows a client node to perform transparent file access over the network. By using NFS, a client node oper-
ates on files residing on a variety of servers and server architectures, and across a variety of operating systems. File access calls on
the client (such as read requests) are converted to NFS protocol requests and sent to the server system over the network. The server
receives the request, performs the actual file system operation, and sends a response back to the client.
NFS operates in a stateless manner using remote procedure calls (RPC) built on top of an external data representation (XDR) protocol. The
RPC protocol enables version and authentication parameters to be exchanged for security over the network.
A server grants access to a specific file system to clients by adding an entry for that file system to the server's file.
A client gains access to that file system using the command to request a file handle for the file system (see mount(1M)). (A file handle
is the means by which NFS identifies remote files.) Once a client mounts the file system, the server issues a file handle to the client
for each file (or directory) the client accesses. If the file is removed on the server side, the file handle becomes stale (dissociated
with a known file), and the server returns an error with set to
A server can also be a client with respect to file systems it has mounted over the network; however, its clients cannot directly access
those file systems. If a client attempts to mount a file system for which the server is an NFS client, the server returns with set to The
client must mount the file system directly from the server on which the file system resides.
The user ID and group ID mappings must be the same between client and server. However, the server maps UID 0 (the superuser) to UID -2
before performing access checks for a client. This process prevents gaining superuser privileges on remote file systems.
RETURN VALUE
Generally, physical disk I/O errors detected at the server are returned to the client for action. If the server is down or inaccessible,
the client receives the message:
where is the hostname of the NFS server. The client continues resending the request until it receives an acknowledgement from the server.
Therefore, the server can crash or power down, and come back up without any special action required by the client. The client process
requesting the I/O will block, but remains sensitive to signals (unless mounted with the option) until the server recovers. However, if
mounted with the option, the client process returns an error instead of waiting indefinitely.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
exportfs(1M), share(1M), mount(1M), mount_nfs(1M), nfsd(1M), mount(2), fstab(4), dfstab(4).
nfs(7)