02-03-2010
erm... because previously the two devices is in the veritas group.
may i need to newfs the c1t1d0 first before i create the mirror
9 More Discussions You Might Find Interesting
1. HP-UX
Being somewhat extremely new to Unix, I have just had a system crash
One of my Volume Groups has crashed
However, this Volume Group is actually mirrored
How do I switch to use the mirrored copy?
Any assistance greatly appreciated
Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies
2. UNIX for Dummies Questions & Answers
I have 2 drives on a sun solaris 8 server that is a live server. I am putting in an additional 2 drives and want to mirror the the first 2. I was thinking of using disksuite but one drive is the root drive with 1 maybe 2 free paritions. The other is only one partition (36G). I was wondering... (2 Replies)
Discussion started by: csgonan
2 Replies
3. UNIX for Dummies Questions & Answers
hi.. newbie here, just wonder why there is a need for mirroring in some servers whereby we already had backups by cron jobs ? (4 Replies)
Discussion started by: Exposure
4 Replies
4. Solaris
Hi all,
Root mirror is broken under veritas control. so could you please help me how to boot the system now step by step procedure. i really thankful to all.
regards
krishna (3 Replies)
Discussion started by: murthy76
3 Replies
5. Solaris
Hi all
Can someone explain to me the different syntax regarding how root / mirror disks are represented. I never truely understand the namely / device tress etc.
Let me give you an example. On one my my servers, the root and mirror drives are :-
A domain on a sunfire 6800 :- ... (6 Replies)
Discussion started by: sbk1972
6 Replies
6. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
7. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
8. Solaris
I have to do patching in single user mode in solaris 10 zfs root pool. Before that I have to detach the root mirror pool so that if patching fails then I can boot from detached root mirror pool. Please let me know how can I detach root pool
bash-3.2# zpool status
pool: rpool
state: ONLINE... (5 Replies)
Discussion started by: hb00
5 Replies
9. Solaris
Got a V490 with one existing root disk. Other disk slot was never populated.
Want to ensure we've got disk mirroring.
Currently vfstab mounts the physical disk - no mirroring set up.
Whats best way to achieve this without losing current disk? (1 Reply)
Discussion started by: psychocandy
1 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)