01-31-2007
your server side must read and write perm.(in file and dire)
for all user after that all user enable for read and write your file
its open for all , you must sure about read and write for all !
pankaj
10 More Discussions You Might Find Interesting
1. OS X (Apple)
Hi all !
I am looking for a command in the terminal or GUI to mount
an NFS drive.
Second , is there any solution to get rid of / " * in old files names
I know it can be done i just dont know how !
Hope that some one can help
Best R.
Yovel (2 Replies)
Discussion started by: yoveln
2 Replies
2. Solaris
While mounting nfs file system I get the following error .
# mount -F nfs jewelex:/back2 /oback2
nfs mount: jewelex:/back2: Permission denied
Following is the permission for oback2
drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2
Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies
3. Linux
Hi,
Re-building linux server from a kickstart image on cdrom.
We have a kickstart server.
the cdrom contacins the kickstart ks.cfg file and does a NFS mount from an IP to load the iso images and other files needed during the kickstart (re-build)
Now for some reason the kickstart stops and... (2 Replies)
Discussion started by: Andrek
2 Replies
4. Solaris
On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line:
share -F nfs -o rw /export/home/data
In the /etc/hosts.equiv file, I have this:
+
When I do a "ps -ef" command, I see that the "nfsd' daemon is started.
... (2 Replies)
Discussion started by: serendipity1276
2 Replies
5. Solaris
:confused:Hi all
When i see in the /var/adm/messages, i saw the following error
unix: NFS write error on host : Stale NFS file handle.
unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49)
It is using sunOS 5.7. Is anybody know what is this error?
Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I need to mount an nfs filesystem as below.
xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs
For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work?
mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
7. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (1 Reply)
Discussion started by: ainstin
1 Replies
8. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (5 Replies)
Discussion started by: ainstin
5 Replies
9. Solaris
Hi,
I am having some issues mounting NFS files.
for some reason the mount -F nfs is not being recognized..
bash-3.2# mount -F nfs -o rw 192.168.245.129:/mnt/nfs1/ /mnt
UX:vxfs mount: ERROR: V-3-20135: FSType nfs not recognized
UX:vxfs mount: INFO: V-3-20147: Usage:
mount {special |... (5 Replies)
Discussion started by: br1an
5 Replies
10. Solaris
Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400)
Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 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)