01-04-2011
Problem with NFS
Hello everyone
I need to share a file system with two Aix boxes, the version is 5.3 tl9.
I create the nfs and I can see the files from both servers, but the problem with one of them is that I can write on the file or If I create a new one I canīt.
On the server that I create the directory I have the 777 permissions. In this one is where I have the problem.
On the server that I have the filesystem I dont have problem, I can create new files and write on them.
Thanks for your comments.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I've mounted one of the file systems on another machine manually on /mnt located on my machine , after finishing my work i want to umount this /mnt , but all the time it says
" nfs umount : /mnt : is busy " ,although it's not.
so i tried to stop & start Nfs services manually (Incld :... (4 Replies)
Discussion started by: nikk
4 Replies
2. UNIX for Advanced & Expert Users
For having shared file system i've been using nfs ,but regarding this i've some problem ,when i execute "df -ak" i can see the shared file system & i can also go there & list files ,but when i want to create anything in this area (Incld. file ,dir ....) i get permission denied. (i've shared related... (6 Replies)
Discussion started by: nikk
6 Replies
3. UNIX for Advanced & Expert Users
I am having problem mounting my nfs mount on my sun solaris 8 through automount using the automaster file. this has been working fine until today, when my workstation tries to mount the nfs
mount the following error is logged in /var/adm/message
NFS lookup failed for server comserv: error 7... (2 Replies)
Discussion started by: hassan2
2 Replies
4. Solaris
I have a NFS share on a Linux server. When I try to mount it on a Solaris 9 server, I get the following message:
nfs mount: <nfs-server-name>: : RPC: Program not registered
I have a few other Sun boxes and I can mount the share on them without any problems. (2 Replies)
Discussion started by: soliberus
2 Replies
5. AIX
hi team
we had a problem in mounting a network file system from source server to target server and we are not able to mount the file system and we checked all the configuration files and we execute the command in the source server
lssrc -a | grep nfsd we found that 2 nfsd in that one is... (5 Replies)
Discussion started by: aixteam
5 Replies
6. AIX
Got a prob..
I am trying to export a directory and mount it on to a server using NFS. My exporting goes fine as I am able to see the shares through "exportfs -v"
But when I am trying to mount the directory on a the client.. I get an error..
"system call error number - 1"
pls help....
... (3 Replies)
Discussion started by: balaji_prk
3 Replies
7. AIX
AIX's NFS client sends requests on high port numbers by default, and
Linux rejects this as the security exposure it is. On AIX i'm use:
nfso -o nfs_use_reserved_ports=1
But how i can setup it in autorun? /etc/rc.local right way ? (1 Reply)
Discussion started by: jess_t03
1 Replies
8. Filesystems, Disks and Memory
I am trying to setup 2 network shares that exist on a server. One of the shares is mounted but when i try to mount the second share I am greeted with:
# mount srv:/data/music /data/music
srv:/data/music: RPCPROG_NFS: RPC: Program not registered
Server Info:
name: srv
#cat /etc/exports:... (0 Replies)
Discussion started by: ezekiel61
0 Replies
9. Solaris
Hi All,
I have shared a directory from Linux machine which will be accessible from other linux servers without any problem. But when I try to access ( ie mount) on other Solaris machine, it is giving below error.
#mount -F nfs IP of nfs server:/share /localmountpoint
nfs mount : mount:... (1 Reply)
Discussion started by: naw_deepak
1 Replies
10. AIX
Hello,
I have a problem with an NFS file system. Both AIX servers are AIX6.1 and uses NFS version 3.
The problem is that at some point the client server cannot connect to the NFS anymore and when i do df -k it displays the message NFS server <server> not responding still trying.
i run the... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
OPEN(5) File Formats Manual OPEN(5)
NAME
open, create - prepare a fid for I/O on an existing or new file
SYNOPSIS
Topen tag[2] fid[2] mode[1]
Ropen tag[2] fid[2] qid[8]
Tcreate tag[2] fid[2] name[28] perm[4] mode[1]
Rcreate tag[2] fid[2] qid[8]
DESCRIPTION
The open request asks the file server to check permissions and prepare a fid for I/O with subsequent read and write messages. The mode
field determines the type of I/O: 0, 1, 2, and 3 mean read access, write access, read and write access, and execute access, to be checked
against the permissions for the file. In addition, if mode has the OTRUNC (0x10) bit set, the file is to be truncated, which requires
write permission (if the file is append-only, and permission is granted, the open succeeds but the file will not be truncated); if the mode
has the ORCLOSE (0x40) bit set, the file is to be removed when the fid is clunked, which requires permission to remove the file from its
directory. If other bits are set in mode they will be ignored. It is illegal to write a directory, truncate it, or attempt to remove it
on close. If the file is marked for exclusive use (see stat(5)), only one client can have the file open at any time. That is, after such
a file has been opened, no other open will succeed until fid has been clunked. All these permissions are checked at the time of the open
request; subsequent changes to the permissions of files do not affect the ability to read, write, or remove an open file.
The create request asks the file server to create a new file with the name supplied, in the directory (dir) represented by fid, and
requires write permission in the directory. The owner of the file is the implied user id of the request, the group of the file is the same
as dir, and the permissions are the value of
(perm&(~0777|0111)) | (dir.perm&perm&0666)
if a regular file is being created and
(perm&~0777) | (dir.perm&perm&0777)
if a directory is being created. This means, for example, that if the create allows read permission to others, but the containing direc-
tory does not, then the created file will not allow others to read the file.
Finally, the newly created file is opened according to mode, and fid will represent the newly opened file. Mode is not checked against the
permissions in perm. The qid for the new file is returned with the create reply message.
Directories are created by setting the CHDIR bit (0x80000000) in the perm.
The names . and .. are special; it is illegal to create files with these names.
It is an error for either of these messages if the fid is already the product of a successful open or create message.
An attempt to create a file in a directory where the given name already exists will be rejected; in this case, the create system call (see
open(2)) uses open with truncation. The algorithm used by create is: first walk to the directory to contain the file. If that fails,
return an error. Next walk to the specified file. If the walk succeeds, send a request to open and truncate the file and return the
result, successful or not. If the walk fails, send a create message. If that fails, it may be because the file was created by another
process after the previous walk failed, so (once) try the walk and open again. For the behavior of create on a union directory, see
bind(2).
ENTRY POINTS
Open and create both generate open messages; only create generates a create message.
OPEN(5)