09-25-2017
looks like your NFS client are not running on both servers giving you trouble...
Why with the given info is uneasy to reply, I would start by looking at the system logs like rc.log ( to see if configured or not and if, errors? ), as it may be ( long time sine last time I touched an HP...) by default they are not..
It not configured the best is to use sam unless you know the way trough command line...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
Is there any command to list samba shared folders in red hat linux 7.2
Thanks in advance
Bache Gowda (0 Replies)
Discussion started by: bache_gowda
0 Replies
2. Linux
Linux OS : Fedora 10 (No graphical mode)
Windows OS : XP and Windows Server NT
I am able to access from my windows to linux using following step
//fedora10 ip
username of admin and password
I am able to view the admin and shared printer of fedora 10.
When i try to enter in the admin... (0 Replies)
Discussion started by: nightmare49
0 Replies
3. UNIX for Dummies Questions & Answers
Hi
I am using red hat linux, In my folder a strange folder is created i.e. " -a " , folder name is preceded with hyphen. Now if i try to remove with rm -rf -1 , i am unable to do it.
Can anyone please let me know how to do it, & what this kind of folder means
Thanks
Sarbjit (3 Replies)
Discussion started by: sarbjit
3 Replies
4. Red Hat
unable to remove shared memory using ipcrm -m in linux
$ ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 32768 root 644 80 2
0x00000000 65537 root ... (4 Replies)
Discussion started by: LinuxLearner
4 Replies
5. Red Hat
Hi,
I am using redhat linux 5.1 - 64bit,
using command
mount -t cifs //192.192.192.192/SW/Ex /192.192.192.192 -o username=test
I am getting below error.
mount: block device //192.192.192.192/SW/Ex is write-protected, mounting read-only
mount: cannot mount block device... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
6. Solaris
Hello Gurus!!
Very recently i tried to mount a USB pen drive onto my solaris 10 (X4170 model) server. As i understand, in ideal scenarios it should get mounted automatically, but it did not happen. Neither anything is shown in "iostat -En" output or "rmformat -l" about the pen drive.
I also... (10 Replies)
Discussion started by: EmbedUX
10 Replies
7. UNIX and Linux Applications
Hi All,
One job in unix server will generate .csv files daily. I need to copy the latest of these .csv file from the unix server to the shared drive/folder in windows through unix script. My shared folder will look something like
W:\some folder(for example). Could any one of you please help... (3 Replies)
Discussion started by: jaya@123
3 Replies
8. Shell Programming and Scripting
We would be migrating unix solaries to Linux redhat.
Basically source is unix and target is linux.
i would like to copy entire file system unix/source/* to target linux/souce/*
but target linux has only folder setup so what ever files copied need to be placed in the linux server with same... (8 Replies)
Discussion started by: balajikalai
8 Replies
9. AIX
Hi,
I followed this procedure in order to mount in AIX a shared folder in windows server 2000.
https://www-304.ibm.com/support/docview.wss?uid=isg3T1012550
Ive tested the shared folder from other windows Server, and its fine.
What Ive do in AIX is:
Logon as root
Under /Home/spss/ I... (2 Replies)
Discussion started by: trevian3969
2 Replies
10. UNIX for Beginners Questions & Answers
Hi everyone,
have a good day to you.
I am trying to use NFS to share a folder between 2 linux systems.
Let's say the server which is sharing the folder is server A and the client which need to access this shared folder is server B.
In server B, i am having a Joe user which UID and GID is 500.... (1 Reply)
Discussion started by: michael_hoang
1 Replies
nfsiod(8) System Manager's Manual nfsiod(8)
NAME
nfsiod, biod - The local NFS compatible asynchronous I/O daemon
SYNOPSIS
nfsiod [ numthreads ]
DESCRIPTION
The nfsiod daemon runs on an NFS compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
server. The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread. If none is
available, the process itself issues the request to the server and waits for the reply.
The optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for most
systems.
When reading, if the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
the process is currently requesting. If the readahead completes before the process asks for that block, then the subsequent read system
call for that data completes immediately and does not have to wait for the NFS request to complete. Read ahead will be triggered again so
the read may find that next block available as well.
When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the process. If
the process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
has to handle a NFS write itself. This means the process has to wait until the server finishes the write. For Tru64 UNIX servers, the NFS
block size is 8Kb and UFS tries to cluster I/O 64Kbs at a time. If the client is running with 7 I/O threads, 8 write requests can be in
progress at once. This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.
Unlike nfsd, each client thread can use either UDP or TCP. However, if TCP mounts are active, the nfsiod process will time out, close idle
TCP connections, and acknowledge any connections closed by the server.
The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos). Because I/O
to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.
The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process. The ps axml command displays
idle I/O threads under PID 0. Idle threads will be waiting on nfsiod_wait. Therefore, if 7 I/O threads are configured, only 1 nfsiod
process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.
FILES
Specifies the command path Specifies the file for logging NFS activity.
RELATED INFORMATION
Commands: nfsd(8), nfsstat(8)
Daemons: async_daemon(2) delim off
nfsiod(8)