12-17-2002
Quote:
Originally posted by LivinFree
On the other hand, if you could utilize a memory-based filestsyem on an HP-UX server, would that be a cheaper way to, say, store transaction logs for a large database? Or any other highly I/O intensive files?
That's all good until you have that one nanosecond burp of electricity and the filesystem is laid to waste.
Ah, Bubble memory. Where are ya when we need ya?
![Smilie Smilie](https://www.unix.com/images/smilies/smile.gif)
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I wanted to make a ramdisk for a opensolaris distro.
I have very little idea of how to create it?
can anyone pls help me out?
Is there any tutorial on creating it on the net???
Also can i make changes to the actual os itself by changing the scripts involved in ramdisk then use it to... (1 Reply)
Discussion started by: wrapster
1 Replies
2. Shell Programming and Scripting
Hi all,
I wanted to know how to modify the size of the ramdisk?
I mean am manipulating a live cd ,for which the file am manipulating is within a ramdisk now due to size constraints i am unable to play around with some stuff....
currently the size of the ram disk is 64M...
I would like to... (1 Reply)
Discussion started by: wrapster
1 Replies
3. Shell Programming and Scripting
I am trying to mount the ramdisk for sorting, and i get the message "ramdisk already defined." What exactly is /dev/ramdisk0 and is it safe to remove it?
# command
sudo -S mktd 60 <<EOF
initiate
EOF
# block of code for mktd
...
&& {
print "ramdisk already defined."
... (1 Reply)
Discussion started by: ChicagoBlues
1 Replies
4. Shell Programming and Scripting
Hi,
I have sort command that sorts in ramdisk created by a script 'mktd' and later unmounted by script 'rmtd'. The platform is AIX.
# code
sudo -E mktd 44 # create ramdisk of size 44GB
sort ... -k1,1 -2,2 ... # sort a file using the ramdisk on keys 1 and 2
sudo -E rmtd # unmount... (1 Reply)
Discussion started by: ChicagoBlues
1 Replies
5. Ubuntu
hi everybody!
i need your help!
i have some problems with "initial ramdisk" (initrd).
i did with instructions of the following link
Linux initial RAM disk (initrd) overview
but my initrd not run.
after loading, it stopped,and failure notice :
"ramdisk : compressed image found at block 0
no... (0 Replies)
Discussion started by: xikechamh
0 Replies
6. AIX
Hi,
Do you know what is the maximum size I can use to create a ramdisk on AIX 5.3? I m pretty sure i've seen somewhere i can use more than 2 Gb but I can't remember where. I need to do some recommandations for one of my customer and they'll need to create a ramdisk of 20 Gb. Can this be done?
... (1 Reply)
Discussion started by: cedric hanquez
1 Replies
7. UNIX for Advanced & Expert Users
Dear all,
I read some articles about initrd, but how to view this process in my computer :(?
Is there anyway to display to the screen or write to the log file? (3 Replies)
Discussion started by: Hannibal2010
3 Replies
LEARN ABOUT SUNOS
ramdisk
ramdisk(7D) Devices ramdisk(7D)
NAME
ramdisk - RAM disk device driver
SYNOPSIS
ramdisk@0:diskname
DESCRIPTION
The ramdisk driver supports numerous ramdisk devices that are created by the system during the boot process (see boot(1M)) or during nor-
mal system operation (see ramdiskadm(1M) for more information).
DEVICE SPECIAL FILES
Each ramdisk can be accessed either as a block device or as a raw device. When accessed as a block device, the normal buffering
mechanism is used when reading from and writing to the device, without regard to physical disk records. Accessing the ramdisk as a raw
device enables direct transmission between the disk and the read or write buffer. A single read or write call usually results in a single
I/O operation, meaning that raw I/O is more efficient when many bytes are transmitted. You can find block files names in /dev/ramdisk. Raw
file names are found in /dev/rramdisk.
There are no alignment or length restrictions on I/O requests to either block or character devices.
ERRORS
EFAULT The argument features a bad address.
EINVAL Invalid argument. EIO. An I/O error occurred.
EPERM Cannot create or delete a ramdisk without write permission on /dev/ramdiskctl.
ENOTTY The device does not support the requested ioctl function.
ENXIO The device did not exist during opening.
EBUSY Cannot exclusively open /dev/ramdiskctl. One or more ramdisks are still open.
EEXIST A ramdisk with the indicated name already exists.
EAGAIN Cannot allocate resource for ramdisk. Try again later.
FILES
/dev/ramdisk/diskname
Block device for ramdisk named diskname.
/dev/rramdisk/diskname
Raw device for ramdisk name diskname
/kernel/drv/ramdisk
32-bit driver
/kernel/drv/ramdisk.conf
Driver configuration file. (Do not alter).
/kernel/drv/sparcv9/ramdisk
64-bit driver
ATTRIBUTES
See attributes(5) for descriptions of the following attribute:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
ramdiskadm(1M), fsck(1M), fstyp(1M), mount(1M), newfs(1M), driver.conf(4), filesystem(5), dkio(7I)
NOTES
The percentage of available physical memory that can be allocated to ramdisks is constrained by the variable rd_percent_physmem. You can
tune the rd_percent_physmem variable in /etc/system. By default, the percentage of available physical memory that can be allocated to
ramdisks is fixed at 25%.
A ramdisk may not be the best possible use of system memory. Accordingly, use ramdisks only when absolutely necessary.
SunOS 5.10 04 Mar 2003 ramdisk(7D)