07-12-2009
Well file systems need not be cluster aware. I can have 2 drives presented to both systems at same time but have only one fs write to that shared disk.
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
I have mirrored SAN volume on my B80 rootvg. Can I just remove the mirror and "Remove a P V from a V G" and it will be a diskless AIX?
Is that going to boot on SAN rootvg volume?
Thanks in advance,
itik (3 Replies)
Discussion started by: itik
3 Replies
2. Filesystems, Disks and Memory
so we have a solrais 9 system attached to an HP SAN.
we are using sssu to do snap clones every hour.
the only problem is the we get write errors on the solrais system every time we do a snap.
from /var/adm/messages
Apr 21 14:37:48 svr001 scsi: WARNING:... (0 Replies)
Discussion started by: robsonde
0 Replies
3. AIX
Hello everyone
I got several aix boxes with aix 5.3
I got a ibm san ds4500
My question is
How can I do a match between my disks on aix and the san?
I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this
If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
4. Solaris
hi all,
have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ??
thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
My main function is as a DBA. Another person manages the server and the SAN.
I just want to know if I should be worried about high disk I/O or is it irrelevant as the I/O "load balancing" will be "taken care" of by the SAN?
For example, I have hdisk1-5 and I can see that there are... (2 Replies)
Discussion started by: newbie_01
2 Replies
6. Solaris
Hi,
I have a production solaris 10 SPARC system (portal). Yesterday legato/Networker gave an I/O Error on one of the files on its SAN mounted disk.
I went to that particular file on the system, did an ls and it showed the file. However, ls -l did not work and it said IO error.
... (6 Replies)
Discussion started by: Mack1982
6 Replies
7. Solaris
Hi All,
I have server : Sun-Fire-V490 configured with Solaris 10 zfs
..
and I have configured three mirror the third one from EMC
storage.
root@server # zpool status -v
pool: rpool
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
... (8 Replies)
Discussion started by: top.level
8 Replies
8. Solaris
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
9. AIX
HACMP two-node cluster with mirrored LVM.
HACMP two-node cluster with two SAN storages mirrored using LVM. Configured 2 disk heartbeat networks - 1 per each SAN storage. While performing redundancy tests. Once one of SAN storage is down - cluster is going to ERROR state. What are the guidelines... (2 Replies)
Discussion started by: OdilPVC
2 Replies
10. UNIX for Beginners Questions & Answers
I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
share(1M) share(1M)
NAME
share - make local resource available for mounting by remote systems
SYNOPSIS
share [-F FSType] [-o specific_options] [-d description] [pathname]
The share command exports, or makes a resource available for mounting, through a remote file system of type FSType. If the option -F FSType
is omitted, the first file system type listed in /etc/dfs/fstypes is used as default. For a description of NFS specific options, see
share_nfs(1M). pathname is the pathname of the directory to be shared. When invoked with no arguments, share displays all shared file sys-
tems.
-F FSType
Specify the filesystem type.
-o specific_options
The specific_options are used to control access of the shared resource. (See share_nfs(1M) for the NFS specific options.) They may be
any of the following:
rw
pathname is shared read/write to all clients. This is also the default behavior.
rw=client[:client]...
pathname is shared read/write only to the listed clients. No other systems can access pathname.
ro
pathname is shared read-only to all clients.
ro=client[:client]...
pathname is shared read-only only to the listed clients. No other systems can access pathname.
Separate multiple options with commas. Separate multiple operands for an option with colons. See .
-d description
The -d flag may be used to provide a description of the resource being shared.
Example 1: Sharing a Read-Only Filesystem
This line will share the /disk file system read-only at boot time.
share -F nfs -o ro /disk
Example 2: Invoking Multiple Options
The following command shares the filesystem /export/manuals, with members of the netgroup having read-only access and users on the speci-
fied host having read-write access.
share -F nfs -o ro=netgroup_name,rw=host1:host2:host3 /export/manuals
/etc/dfs/dfstab
list of share commands to be executed at boot time
/etc/dfs/fstypes
list of file system types, NFS by default
/etc/dfs/sharetab
system record of shared file systems
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mountd(1M), nfsd(1M), share_nfs(1M), shareall(1M), unshare(1M), attributes(5)
Export (old terminology): file system sharing used to be called exporting on SunOS 4.x, so the share command used to be invoked as
exportfs(1B) or /usr/sbin/exportfs.
If share commands are invoked multiple times on the same filesystem, the last share invocation supersedes the previous--the options set by
the last share command replace the old options. For example, if read-write permission was given to usera on /somefs, then to give read-
write permission also to userb on /somefs:
example% share -F nfs -o rw=usera:userb /somefs
This behavior is not limited to sharing the root filesystem, but applies to all filesystems.
9 Dec 2004 share(1M)