10-02-2012
If you get errors writing to a disk, it's toast. Either that, or your disk controller or drivers for it are having trouble (generally unlikely). Reality trumps diagnostics.
Swap is overflow space when you're low on memory. Linux does not require as much swap space as RAM, but some kinds of UNIX demand that there be enough swap to save all RAM if need be.
Mounting is the process which converts a disk device into a folder you can use. The device and the folder are actually managed separately. Windows doesn't really give you access to the device and mounts everything itself unasked onto a generic drive letter, UNIX is both stricter and more flexible. There's no drive letters, partitions are mounted inside folders, whichever folders you want. /home will often be its own separate partition, for example.
Last edited by Corona688; 10-02-2012 at 02:13 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused: Im as newbie as they come.......
I just loaded Red Hat 8.0 on my computer. I have a second hard drive that i reformatted with a Fat32 so I could share it with my XP and Linux partions....... I have like 4000 mp3's on it and i would like to get it to auto mount when Linux boots....?
Or... (5 Replies)
Discussion started by: mynameiskyle
5 Replies
2. SCO
I trying to learn Unix and I am using SCO Unixware 7.1. Below are three question that I have:
1) Can someone tell me what command I can use to find out the system processor speed.
2) Can someone tell me what command I can use to find out what's the hard drive size of my unix box.
3) Can... (1 Reply)
Discussion started by: etaup02
1 Replies
3. UNIX for Dummies Questions & Answers
:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows......
dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/????????
Where I have the question marks is the problem.
How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies
4. Filesystems, Disks and Memory
Hi
I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies
5. AIX
Good day,
I have an rs/6000 server, model 7044-270. I bought a 2nd hard drive for it but im not sure its the right one. (fru:H13060) As you surely know, the 7044-270 hard drives are put in some sort of tray/carrier. There is a cable that will interface the HDD with the tray/carrier so the... (0 Replies)
Discussion started by: Netghost
0 Replies
6. Filesystems, Disks and Memory
Hi,
I just set up a raid Z array in solaris xpress and I notice that the drives feel pretty damn hot. I use speedfan to monitor the temperatures of the hard drives in XP. Is there a similar program for solrais? I assume there would be since the drives all have temp sensors in them, but I... (2 Replies)
Discussion started by: ciscocbee
2 Replies
7. Solaris
Hi
When I installed opensolaris, I installed it on a 20GB partition. How do I make use of the other 300GB I have spare?
format shows:-
-bash-3.2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c3d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
... (12 Replies)
Discussion started by: hellotommy
12 Replies
8. Solaris
Version: solaris 10 x86
I just got a western digital external harddrive formated with fat 32. this drive came with some setup files which is meant for windows or mac.
I want to reformat and partition this drive into two ( for solaris and windows) such that the setup files will still be there... (2 Replies)
Discussion started by: seyiisq
2 Replies
9. Filesystems, Disks and Memory
Hi guys, I have been looking around and searching for the past hour and did not see anything. but please forgive me if I missed something.
I had a sparc 10 ultra cpu die on me, I got a replacement server from a very generous guy here, now I am getting around to remounting my old hard drive with... (0 Replies)
Discussion started by: DrDarkMatter
0 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)