07-11-2012
Cool thx for the fast reply
10 More Discussions You Might Find Interesting
1. Solaris
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Discussion started by: simquest
1 Replies
2. Solaris
I tried to use zfs .. only for test ..so when I take my test disks into zfs pool their VTOC changed .. and 7th slice does not appear now. How can I restore default VTOC to my disks.
my machine is x86 .. SunFire X4200 .. so this disks do not have slices like sparc machines .. they have... (6 Replies)
Discussion started by: samar
6 Replies
3. Solaris
I 'm having problem in importing a zfs pool was getting error device missing and upon further digging found that labels on my disk for zpool are missing
Does anyone know how to recover from it ?
root@essapl020-u006 # zdb -l /dev/dsk/emcpower0c
--------------------------------------------... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Ubuntu
My PC (Esprimo, 3 yeas old) has one hard drive having 2 partitions C: (80 GB NTFS, XP) and D: (120 GB NTFS, empty) and and a 200 MB area that yet is not-partitioned.
I would like to try Ubuntu and to install Ubuntu on the not-partitioned area . The idea is to have the possibility to run... (7 Replies)
Discussion started by: C.Weidemann
7 Replies
5. Solaris
Hello,
we have a machine with Solaris Express 11, 2 LSI 9211 8i SAS 2 controllers (multipath to disks), multiport backplane, 16 Seagate Cheetah 15K RPM disks.
Each disk has a sequential performance of 220/230 MB/s and in fact if I do a
dd if=/dev/zero of=/dev/rdsk/<diskID_1> bs=1024k... (1 Reply)
Discussion started by: golemico
1 Replies
6. Solaris
we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label.
now we want to mount this file system into an LDOM.
my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies
7. Solaris
Hi,
How to to make a slice and define as ufs from zpool? Please advice me.
Thanks.
---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ----------
Before slice:
Part Tag Flag Cylinders Size Blocks
0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies
8. Solaris
Hello,
I am upgrading Veritas from 5.1 to 6.0.1/6.0.5 in a Solaris 10 u8 server with OS mirrored (rpool) in zfs/zpool configuration.
I need to split it to have a quick way to backout in case of failure (make splitted mirror side bootable for a quick revert, like booting from it). I remember... (3 Replies)
Discussion started by: feroccimx
3 Replies
9. Solaris
hi,
have no a lot of experience with zfs so perhaps the question is quite simple but i didn't find any reasonable info how to resolve it.
thus, fresh solaris installation
14GB in 86 files copied after that got msg No space left on device (28) in spite of according to stat there is... (4 Replies)
Discussion started by: bindto
4 Replies
10. Ubuntu
What is the recommended way to upgrade ZFS on Ubuntu 16.04? i have read this thread, but the PPA is not safe?
Ubuntu 16.04, ZFS 0.7.3 anyone got it running? : zfs (7 Replies)
Discussion started by: kebabbert
7 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)