07-13-2009
You CAN have both be able to have ACCESS to the drive. However, it is NOT true that one can be read+write and the other read only. The only way this is safe is if one system is NOT using (and if possible, seeing) the drive at the same time. Why? Because manipulations to the drive can happen from the system that has read+write including modifications to meta data areas... and if that information is not communicated somehow to the other host, then even if it's supposedly "read only", you'll be messing up the internal representation on that host and possible cause issues, perhaps major issues.
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
RP(4) Kernel Interfaces Manual RP(4)
NAME
rp - RP-11/RP03 moving-head disk
DESCRIPTION
The files rp0 ... rp7 refer to sections of RP disk drive 0. The files rp8 ... rp15 refer to drive 1 etc. This allows a large disk to be
broken up into more manageable pieces.
The origin and size of the pseudo-disks on each drive are as follows:
disk start length
0 0 81000
1 0 5000
2 5000 2000
3 7000 74000
4-7 unassigned
Thus rp0 covers the whole drive, while rp1, rp2, rp3 can serve usefully as a root, swap, and mounted user file system respectively.
The rp files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are
transmitted. The names of the raw RP files begin with rrp and end with a number which selects the same disk section as the corresponding
rp file.
In raw I/O the buffer must begin on a word boundary.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
hp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
RP(4)