Sponsored Content
Operating Systems Solaris How to mount a shared LUN between two hosts? Post 302860613 by aliyesami on Sunday 6th of October 2013 06:31:37 PM
Old 10-06-2013
no iam not using any clustered filesystem .
so you can't ufs mount a shared lun accross node on OS level ?
i have mounted the luns read/write cause i can create files on them on each node.

regards
 

10 More Discussions You Might Find Interesting

1. Solaris

ssh with shared mount point

I have 3 nodes and I want to set up ssh between them. Normnally I am fine with that but I am a bit stumped because for the Oracle user we have a shared mountpoint (/home/oracle) across all 3 nodes I create my rsa and dsa files in ~/.shh as node1_id_rsa / node1_id_dsa (for each of the 3 modes)... (4 Replies)
Discussion started by: devjxh
4 Replies

2. UNIX for Advanced & Expert Users

solaris 10 autofs - how to mount /net (hosts)

Hello Everyone, I am working with Solaris 10 autofs feature. On the server (and client) in /etc/auto_master I have this entry: /net -hosts -nosuid,nobrowse On the server, I have shared out /var/tmp, started the nfs server and issued the shareall command. When I issue share I can... (1 Reply)
Discussion started by: anies rahman
1 Replies

3. Solaris

I have LUN ID, how to find disk relate to that LUN ID?

I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer. thanks (4 Replies)
Discussion started by: uuontario
4 Replies

4. AIX

Mount a SAN LUN which contains clone copy - AIX 6.1

Hello Everyone, Can someone help me to mount a SAN hdisk which contains a clone data copy(san) of the remote server to the another machine. Both servers are running in AIX. Thanks in advance ! Regards, Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies

5. Solaris

import lun data to mount point - Solaris 10

Hi Guys, I have EMC Storage and from this storage I have maped lun5 to Sun Solaris server and I have created on this lun mount point with name /application I have anothere Sun Solaris server and I'll colne lun5 to lun10 from storage level so the data of lun5 will be in lun10 how to... (6 Replies)
Discussion started by: Mr.AIX
6 Replies

6. Red Hat

Need to mount LUN on two linux boxs (one rw the other ro) caveat details inside

Calling all Linux GURU's. The purpose of this thread is to try an recreate what we already have stood up in my environment, however the steps i am having to produce my own. I have got multiple applications that dump the data to various LUNs, the LUNs are managed by an Enterprise SAN... (11 Replies)
Discussion started by: jcejka
11 Replies

7. HP-UX

Shared a Disk between two hosts

Hello people. I need to shared a disk between two virtuals hosts in the same Guest, and I don't see any help about this. I'm working on HP-UX 11.31 Thanks to all.:b: (2 Replies)
Discussion started by: cegamboav
2 Replies

8. Linux

Mount a newly added LUN on a GNU/Linux distro

Hi I am not familiar with the linux, but I was asked to create a file system on a LUN from the NetApp that was mapped to the linux server. The server is runing: uname -a Linux localhost.localdomain 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux and now... (6 Replies)
Discussion started by: fretagi
6 Replies

9. HP-UX

Unable to mount shared folder from Linux server

Hi all, I have 3 servers, rx2600, rx2600, and rx2660. I have another x86 server running on Suse, and create a shared folder named /public From 1 of the rx2600 server I can mount that shared folder : intaqa:/>mount 10.1.2.82:/public /bkup intaqa:/>cd /bkup But from 2 others server I... (29 Replies)
Discussion started by: rexmale
29 Replies

10. Solaris

How to copy a tar file on a series of remote hosts and untar it on those hosts?

Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh. Actions to perform within a single ssh session via shell script - copy a file - untar at destination (remote host) OS : Linux RHEL6 (3 Replies)
Discussion started by: sankasu
3 Replies
MOUNT(8)						      System Manager's Manual							  MOUNT(8)

NAME
mount - mount file systems SYNOPSIS
mount [ -adfruvw ] [ -t ufs | external_type ] mount [ -dfruvw ] special | node mount [ -dfruvw ] [ -o options ] [ -t ufs | external_type ] special node DESCRIPTION
The mount command calls the mount(2) system call to prepare and graft a special device on to the file system tree at the point node. If either special or node are not provided, the appropriate information is taken from the fstab(5) file. The system maintains a list of currently mounted file systems. If no arguments are given to mount, this list is printed. The options are as follows: -a Causes everything to be done except for the actual system call. This option is useful in conjunction with the -v flag to determine what the mount command is trying to do. -f Forces the revocation of write access when trying to downgrade a filesystem mount status from read-write to read-only. For 2.11BSD this flag is currently not implemented. -o Options are specified with a -o flag followed by a comma separated string of options. The following options are available: async All I/O to the file system should be done asynchronously. This is a dangerous flag to set, and should not be used unless you are prepared to recreate the file system should your system crash. force The same as -f; forces the revocation of write access when trying to downgrade a filesystem mount status from read- write to read-only. This is not (and likely never will be) supported in 2.11BSD. nodev Do not interpret character or block special devices on the file system. This option is useful for a server that has file systems containing special devices for architectures other than its own. noexec Do not allow execution of any binaries on the mounted file system. This option is useful for a server that has file systems containing binaries for architectures other than its own. nosuid Do not allow set-user-identifier or set-group-identifier bits to take effect. rdonly The same as -r; mount the file system read-only (even the super-user may not write it). sync All I/O to the file system should be done synchronously. update The same as -u; indicate that the status of an already mounted file system should be changed. Any additional options specific to a filesystem type that is not one of the internally known types (see the -t option) may be passed as a comma separated list; these options are distinguished by a leading - (dash). Options that take a value are specified using the syntax -option=value. At present no 2.11BSD mount options use the following form, the example has been retained for illustrative purposes only. For example, the mount command: mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp causes mount to execute the equivalent of: /sbin/mount_mfs -o nosuid -N -s 4000 /dev/dk0b /tmp -r The file system is to be mounted read-only. Mount the file system read-only (even the super-user may not write it). The same as the ``rdonly'' argument to the -o option. -t "ufs | external type" The argument following the -t is used to indicate the file system type. The type ufs is the default. Ufs is also the only value supported by 2.11BSD other than swap. Thus the -t will rarely be used. The -t option can be used to indicate that the actions should only be taken on filesystems of the specified type. More than one type may be specified in a comma separated list. The list of filesystem types can be prefixed with ``no'' to specify the filesystem types for which action should not be taken. For example, the mount command: mount -a -t nonfs,mfs mounts all filesystems except those of type NFS and MFS. If the type is not one of the internally known types, mount will attempt to execute a program in /sbin/mount_XXX where XXX is replaced by the type name. For example, mfs filesystems are mounted by the program /sbin/mount_mfs. -u The -u flag indicates that the status of an already mounted file system should be changed. Any of the options discussed above (the -o option) may be changed; also a file system can be changed from read-only to read-write or vice versa. An attempt to change from read-write to read-only will fail if any files on the filesystem are currently open for writing unless the -f flag is also specified. This is currently not implemented in 2.11BSD. The ability to change the flags (nodev, nosuid, etc) is however supported. The set of options is determined by first extracting the options for the file system from the fstab table, then applying any options specified by the -o argument, and finally applying the -r or -w option. -v Verbose mode. -w The file system object is to be read and write. FILES
/etc/fstab file system table SEE ALSO
mount(2), fstab(5), umount(8) BUGS
It is possible for a corrupted file system to cause a crash. mount and this manpage were ported from 4.4BSD-Lite to 2.11BSD to gain the ability to set the various flags such as nodev, nosuid and so on. Multiple filesystem types are not supported and several of the options and flags are not implemented. HISTORY
A mount command appeared in Version 6 AT&T UNIX. 4.4 Berkeley Distribution November 16, 1996 MOUNT(8)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy