Sponsored Content
Full Discussion: Mounted Root Filesystem
Top Forums UNIX for Advanced & Expert Users Mounted Root Filesystem Post 96059 by jimthompson on Tuesday 17th of January 2006 09:27:30 AM
Old 01-17-2006
Mounted Root Filesystem

In my Solaris 10 based server, I have noticed the following mounts when a use DF -K

/dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% /
/ 5062414 3213876 1797914 65% /net/se420

I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect. However I do not understand the second mount as it appears to be a duplicate mount of the root partition. Also it does not appear in my vfstab. When I manually dismount this mount point and then reboot the server - it is remounted !

What is this second mount, where is it being auto mounted and do I need it anyway ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can I tell if a filesystem is NFS mounted?

I would like to know if there is a command or set of commands that I can run to verify that there are no 'extraneous' nfs mounted filesystems on our server. I didn't see anything in doing a search on NFS. We think that we may have some filesystems that are still nfs mounted when the link should... (3 Replies)
Discussion started by: giannicello
3 Replies

2. Shell Programming and Scripting

Testing if nfs filesystem is mounted

Hello, I have a backup script that backs up my system to a nfs mounted file system. The mount point on my local system is /backup. I want my script to check whether the nfs file system is mounted on /backup before actually backing anything up. Even if the nfs file system was NOT mounted,... (2 Replies)
Discussion started by: xadamz23
2 Replies

3. UNIX for Dummies Questions & Answers

/ filesystem is mounted read only

how do you fsck the / filesystem? I know it does it automatically the next time I boot up following a switch on the wall shutdown but is there a flad somewhere that forces this on next boot up? Thanks (2 Replies)
Discussion started by: DGK
2 Replies

4. Filesystems, Disks and Memory

How to find the time a filesystem was mounted without using root privileges

Hi, Im running RHEL. How do I find the time a particular filesystem was mounted? Please Let me know Thanks (1 Reply)
Discussion started by: neuralninja
1 Replies

5. UNIX for Advanced & Expert Users

How to find the time a filesystem was mounted without using root privileges

Hi, Im running RHEL. How do I find the time a particular filesystem was mounted? Please Let me know Thanks (1 Reply)
Discussion started by: neuralninja
1 Replies

6. Solaris

UFS filesystem mounted on 2 hosts question

I have two Unix (Solaris) hosts that are both attached to our SAN. They are both presented with the same luns. What I want to do is have the same UFS filesystem mounted on both hosts at the same time. What I am trying to accomplish is creating a zone that will reside on both hosts but only... (2 Replies)
Discussion started by: beaker457
2 Replies

7. Red Hat

doubt in NFS mounted filesystem in linux

Hi, I have some filesystem which is nfs mounted and shared to other servers. Nfs server name= nfsserver (here filesystem is locally mounted) server name where filesystem is shared = sharedserver1 and sharedserver2 filesystem which is shared = /filesystem1 when i am checking utilization by... (1 Reply)
Discussion started by: anshu ranjan
1 Replies

8. Shell Programming and Scripting

Check if NAS filesystem is mounted

Anyone know the best way to check and see if a NAS filesystem is mounted on a linux box. I have no idea where to start :wall:. (2 Replies)
Discussion started by: d3mon_spawn
2 Replies

9. Solaris

Have mounted a filesystem in /var and now cannot log in

hi, i might not be posting my question in the right place because i don't know where to post questions my question is like this i created a partition named 'var' in the SOLARIS os .,and then i knowingly mounted it on /var ..now after doing this am not able to login to my... (4 Replies)
Discussion started by: shekhar_4_u
4 Replies

10. AIX

Filesystem Mounted at the server

Hello Gurus, Can you please suggest what is the command of all the filesystems which are mounted at the server. Thanks- Pokhraj Das (1 Reply)
Discussion started by: pokhraj_d
1 Replies
scdpm(1M)						  System Administration Commands						 scdpm(1M)

NAME
scdpm - manage disk path monitoring daemon SYNOPSIS
scdpm [-a] {node | all} scdpm -f filename scdpm -m {[node | all][:/dev/did/rdsk/]dN | [:/dev/rdsk/]cNtXdY | all} scdpm -n {node | all} scdpm -p [-F] {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} scdpm -u {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scdpm command manages the disk path monitoring daemon in a cluster. You use this command to monitor and unmonitor disk paths. You can also use this command to display the status of disk paths or nodes. All of the accessible disk paths in the cluster or on a specific node are printed on the standard output. You must run this command on a cluster node that is online and in cluster mode. You can specify either a global disk name or a UNIX path name when you monitor a new disk path. Additionally, you can force the daemon to reread the entire disk configuration. You can use this command only in the global zone. OPTIONS
The following options are supported: -a Enables the automatic rebooting of a node when all monitored disk paths fail, provided that the following conditions are met: o All monitored disk paths on the node fail. o At least one of the disks is accessible from a different node in the cluster. You can use this option only in the global zone. Rebooting the node restarts all resource and device groups that are mastered on that node on another node. If all monitored disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot again. However, if any monitored disk paths become available after the node reboots but then all monitored disk paths again fail, the node automatically reboots again. You need solaris.cluster.device.admin role-based access control (RBAC) authorization to use this option. See rbac(5). -F If you specify the -F option with the -p option, scdpm also prints the faulty disk paths in the cluster. The -p option prints the cur- rent status of a node or a specified disk path from all the nodes that are attached to the storage. -f filename Reads a list of disk paths to monitor or unmonitor in filename. You can use this option only in the global zone. The following example shows the contents of filename. u schost-1:/dev/did/rdsk/d5 m schost-2:all Each line in the file must specify whether to monitor or unmonitor the disk path, the node name, and the disk path name. You specify the m option for monitor and the u option for unmonitor. You must insert a space between the command and the node name. You must also insert a colon (:) between the node name and the disk path name. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -m Monitors the new disk path that is specified by node:diskpath. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -n Disables the automatic rebooting of a node when all monitored disk paths fail. You can use this option only in the global zone. If all monitored disk paths on the node fail, the node is not rebooted. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -p Prints the current status of a node or a specified disk path from all the nodes that are attached to the storage. You can use this option only in the global zone. If you also specify the -F option, scdpm prints the faulty disk paths in the cluster. Valid status values for a disk path are Ok, Fail, Unmonitored, or Unknown. The valid status value for a node is Reboot_on_disk_failure. See the description of the -a and the -n options for more information about the Reboot_on_disk_failure status. You need solaris.cluster.device.read RBAC authorization to use this option. See rbac(5). -u Unmonitors a disk path. The daemon on each node stops monitoring the specified path. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). EXAMPLES
Example 1 Monitoring All Disk Paths in the Cluster Infrastructure The following command forces the daemon to monitor all disk paths in the cluster infrastructure. # scdpm -m all Example 2 Monitoring a New Disk Path The following command monitors a new disk path.All nodes monitor /dev/did/dsk/d3 where this path is valid. # scdpm -m /dev/did/dsk/d3 Example 3 Monitoring New Disk Paths on a Single Node The following command monitors new paths on a single node. The daemon on the schost-2 node monitors paths to the /dev/did/dsk/d4 and /dev/did/dsk/d5 disks. # scdpm -m schost-2:d4 -m schost-2:d5 Example 4 Printing All Disk Paths and Their Status The following command prints all disk paths in the cluster and their status. # scdpm -p schost-1:reboot_on_disk_failure enabled schost-2:reboot_on_disk_failure disabled schost-1:/dev/did/dsk/d4 Ok schost-1:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d5 Unmonitored schost-2:/dev/did/dsk/d6 Ok Example 5 Printing All Failed Disk Paths The following command prints all of the failed disk paths on the schost-2 node. # scdpm -p -F all schost-2:/dev/did/dsk/d4 Fail Example 6 Printing the Status of All Disk Paths From a Single Node The following command prints the disk path and the status of all disks that are monitored on the schost-2 node. # scdpm -p schost-2:all schost-2:reboot_on_disk_failure disabled schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok EXIT STATUS
The following exit values are returned: 0 The command completed successfully. 1 The command failed completely. 2 The command failed partially. Note - The disk path is represented by a node name and a disk name. The node name must be the host name or all. The disk name must be the global disk name, a UNIX path name, or all. The disk name can be either the full global path name or the disk name: /dev/did/dsk/d3 or d3. The disk name can also be the full UNIX path name: /dev/rdsk/c0t0d0s0. Disk path status changes are logged with the syslogd LOG_INFO facility level. All failures are logged with the LOG_ERR facility level. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevice(1CL), clnode(1CL), attributes(5) Sun Cluster System Administration Guide for Solaris OS Sun Cluster 3.2 22 Jun 2006 scdpm(1M)
All times are GMT -4. The time now is 08:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy