Sponsored Content
Operating Systems Solaris Sol 10 - Strange NFS behaviour - adminnfs prefix to mount point Post 303006379 by gull04 on Wednesday 1st of November 2017 07:45:16 AM
Old 11-01-2017
Hi,

Bit of a historical memory here, but you may want to check what the NFSMAPID is set to - it should be a domain from memory but......

Also might be worth considering a restart of the mapid service as it may stale.

Regards

Gull04

Last edited by gull04; 11-01-2017 at 08:52 AM.. Reason: Additional Information.
 

10 More Discussions You Might Find Interesting

1. Linux

one nfs mount point for many logical volumes

hi i am wondering if it is possible to use one nfs mount point for several logical volumes. i have a top level directory /imaging with data1 - data50 below it. each dataX directory is a logical volume configured through LVM. if i mount them separately on the client (i.e. 50 lines in fstab... (1 Reply)
Discussion started by: user23
1 Replies

2. AIX

NFS mount point monitoring script

Hi, I'm looking to create a NFS mount point monitoring shell script not sure if im going the right way about it so could do with some help. What i was thinking of doing was using the below command but am unsure how to handle the output. So if the filesyetem is active it will return "1" but if... (4 Replies)
Discussion started by: elmesy
4 Replies

3. Red Hat

NFS mount point problem

Hi Forum I am trying to mount /NFS as nfs mountpoint on two servers ( A & B ). After mounting the nfs filesystem, both of them behave normally for around 10 mins and after that the NFS file handle become stale and the mountpoints dont respond. While executing df -kh, the output hang out and the... (15 Replies)
Discussion started by: rajdasuwal
15 Replies

4. Solaris

No write permission on NFS mount point

hi all i have mounted one nfs mount point but i has no write permission on it. when i am going to make a directory it is giving an error # mkdir 1 mkdir: Failed to make directory "1"; Permission denied i shared using command # share -F nfs -o rw -d "backup" /backup mounted using... (3 Replies)
Discussion started by: nikhil kasar
3 Replies

5. Shell Programming and Scripting

Script for NFS mount point

Hi , i have create the bash script for nfs but in this script asking for mount point only once it is it prompting for second time. example: do you wants to create any other mount point ? note(if i give yes it should ask me to add the mount point else it should proceed with next step) it... (5 Replies)
Discussion started by: Rahulne25
5 Replies

6. Red Hat

NFS mount point

Hi, Can you tell me something about NFS mount point ? Regards, Maddy (3 Replies)
Discussion started by: Maddy123
3 Replies

7. Red Hat

Regarding NFS mount point

Dear All, We have two different mount points in Linux NFS one is 15 TB and another one is 15 TB. Can we club both of the two mount points and club in to a single volume in Linux. As we need to restore Database in that single volume. Kindly help us on this. Regards , rj (10 Replies)
Discussion started by: jegaraman
10 Replies

8. UNIX for Beginners Questions & Answers

How to create a new mount point with 600GB and add 350 GBexisting mount point? IN AIX

How to create a new mount point with 600GB and add 350 GBexisting mount point Best if there step that i can follow or execute before i mount or add diskspace IN AIX Thanks (2 Replies)
Discussion started by: Thilagarajan
2 Replies

9. AIX

AIX lsvg strange LV STATE and MOUNT POINT

What does it mean when your LV STATE changes to closed/syncd? What does it mean when your mount point is #? I was not able to mount it or write data to it. So in this case since there was no data in /opt/cvt I used rmlv to get rid of it. Why did I have to manually edit /etc/filesystems to get rid... (1 Reply)
Discussion started by: cokedude
1 Replies

10. UNIX for Advanced & Expert Users

Mount Point goes into a very strange state.

Hi Guys, This one has got me completely baffled and after some fairly lengthy searching online and in the forum, I think I should share this with you - after all someone is bound to have seen this? So the story so far, I've built a couple of RHEL 7.5 servers, these are HP DL360 G10's with two... (4 Replies)
Discussion started by: gull04
4 Replies
sv(8)							      System Manager's Manual							     sv(8)

NAME
sv - control and manage services monitored by runsv(8) SYNOPSIS
sv [-v] [-w sec] command services /etc/init.d/service [-w sec] command DESCRIPTION
The sv program reports the current status and controls the state of services monitored by the runsv(8) supervisor. services consists of one or more arguments, each argument naming a directory service used by runsv(8). If service doesn't start with a dot or slash and doesn't end with a slash, it is searched in the default services directory /etc/service/, otherwise relative to the current directory. command is one of up, down, status, once, pause, cont, hup, alarm, interrupt, 1, 2, term, kill, or exit, or start, stop, restart, shutdown, force-stop, force-reload, force-restart, force-shutdown. The sv program can be sym-linked to /etc/init.d/ to provide an LSB init script interface. The service to be controlled then is specified by the base name of the ``init script''. COMMANDS
status Report the current status of the service, and the appendant log service if available, to standard output. up If the service is not running, start it. If the service stops, restart it. down If the service is running, send it the TERM signal, and the CONT signal. If ./run exits, start ./finish if it exists. After it stops, do not restart service. once If the service is not running, start it. Do not restart it if it stops. pause cont hup alarm interrupt quit 1 2 term kill If the service is running, send it the STOP, CONT, HUP, ALRM, INT, QUIT, USR1, USR2, TERM, or KILL signal respectively. exit If the service is running, send it the TERM signal, and the CONT signal. Do not restart the service. If the service is down, and no log service exists, runsv(8) exits. If the service is down and a log service exists, send the TERM signal to the log service. If the log service is down, runsv(8) exits. This command is ignored if it is given to an appendant log service. sv actually looks only at the first character of these commands. Commands compatible to LSB init script actions status Same as status. start Same as up, but wait up to 7 seconds for the command to take effect. Then report the status or timeout. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and available; it's considered to be avail- able if ./check exits with 0. stop Same as down, but wait up to 7 seconds for the service to become down. Then report the status or timeout. reload Same as hup, and additionally report the status afterwards. restart Send the commands term, cont, and up to the service, and wait up to 7 seconds for the service to restart. Then report the status or timeout. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and avail- able again; it's considered to be available if ./check exits with 0. shutdown Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status or timeout. force-stop Same as down, but wait up to 7 seconds for the service to become down. Then report the status, and on timeout send the service the kill command. force-reload Send the service the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the status, and on timeout send the service the kill command. force-restart Send the service the term, cont and up commands, and wait up to 7 seconds for the service to restart. Then report the status, and on timeout send the service the kill command. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and available again; it's considered to be available if ./check exits with 0. force-shutdown Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status, and on timeout send the ser- vice the kill command. try-restart if the service is running, send it the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the status or timeout. Additional Commands check Check for the service to be in the state that's been requested. Wait up to 7 seconds for the service to reach the requested state, then report the status or timeout. If the requested state of the service is up, and the script ./check exists in the service direc- tory, sv runs this script to check whether the service is up and running; it's considered to be up if ./check exits with 0. OPTIONS
-v If the command is up, down, term, once, cont, or exit, then wait up to 7 seconds for the command to take effect. Then report the status or timeout. -w sec Override the default timeout of 7 seconds with sec seconds. This option implies -v. ENVIRONMENT
SVDIR The environment variable $SVDIR overrides the default services directory /etc/service/. SVWAIT The environment variable $SVWAIT overrides the default 7 seconds to wait for a command to take effect. It is overridden by the -w option. EXIT CODES
sv exits 0, if the command was successfully sent to all services, and, if it was told to wait, the command has taken effect to all ser- vices. For each service that caused an error (e.g. the directory is not controlled by a runsv(8) process, or sv timed out while waiting), sv increases the exit code by one and exits non zero. The maximum is 99. sv exits 100 on error. If sv is called with a base name other than sv: it exits 1 on timeout or trouble sending the command; if the command is status, it exits 3 if the service is down, and 4 if the status is unknown; it exits 2 on wrong usage, and 151 on error. SEE ALSO
runsv(8), chpst(8), svlogd(8), runsvdir(8), runsvchdir(8), runit(8), runit-init(8) http://smarden.org/runit/ AUTHOR
Gerrit Pape <pape@smarden.org> sv(8)
All times are GMT -4. The time now is 12:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy