Sponsored Content
Full Discussion: Swap file system
Top Forums UNIX for Advanced & Expert Users Swap file system Post 302315227 by jlliagre on Tuesday 12th of May 2009 12:43:26 AM
Old 05-12-2009
The system will likely leave the disk failure unnoticed if the swap space isn't used which is the usual case.
Otherwise, I suspect a panic for unrecoverable read errors and possibly something less extreme for write errors.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

What swap is my system running on?

hi all, i need to know what swap my system is running on... Sun-Fire-880 is my system... physical memory= 16GB (8 CPU's) i know generally we keep swap 2 times of real memory... i want to know what is current swap my system is running? following is the o/p of swap -s: Wed Mar 29 16:08:08... (4 Replies)
Discussion started by: abhijeetkul
4 Replies

2. Solaris

/tmp: File system full, swap space limit exceeded

Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again. The server has not rebooted but here are the first errors in the messages log... (5 Replies)
Discussion started by: frustrated1
5 Replies

3. Solaris

Swap config - Mirror swap or not?

Hello and thanks in advance. I have a Sun box with raid 1 on the O/S disks using solaris svm. I want to unmirror my swap partition, and add the slice on the second disk as an additional swap device. This would give me twice as much swap space. I have been warned not to do this by some... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

4. Solaris

swap space in veritas file system

hi every one , i know how to add swap space in ufs file system. but i m facing problem in veritas file system . i wants to know how will i create swap or add new swap space in existing swap space . Note: disk under veritas volume manager control . please help me to solve this issue . (5 Replies)
Discussion started by: samy123
5 Replies

5. Filesystems, Disks and Memory

How To setup a Diskless Swap System.

This is a guide for setting up your computer with a fast swap system using usb memory sticks. A detailed study of the theories behind this setup can be found here. While this How-To does not include the CFLRU replacement algorithm, it does show the performance benefits of using NAND flash memory... (2 Replies)
Discussion started by: Johnny_Thumbs
2 Replies

6. HP-UX

Swap device file and swap sapce

Hi I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system: - I would like to know when does the memory swap space spill over to the device swap space? - And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Discussion started by: lamoul
6 Replies

7. Solaris

increase SWAP on ZFS file system

Hi All, I am using this commands to dynamically increase ZFS swap space on Solaris my question is: 1- after i make these commands it will permanent or it will remove after restart 2- how to make it permanent # swap -l swapfile dev swaplo bloques libre /dev/zvol/dsk/rpool/swap... (4 Replies)
Discussion started by: osmanux
4 Replies

8. UNIX for Dummies Questions & Answers

swap issues, system is running at 99%

Hi All, I am trying to understand why my system is running at very high. This system is almost out of memory. See below. swapon -s Filename Type Size Used Priority /dev/mapper/VolGroup00-LogVol02 partition 8388600 8235088 -1... (2 Replies)
Discussion started by: samnyc
2 Replies

9. Solaris

File system full, swap

hi all I am having a t5240 server in that zone is there in /var/adm/messages i am getting the following warning WARNING: /zoneroot/zonename-zone/root/tmp: File system full, swap space limit exceeded if a swap is getting full what can i do. Please use code tags next time for your... (2 Replies)
Discussion started by: nikhil kasar
2 Replies

10. Solaris

Explain the output of swap -s and swap -l

Hi Solaris Folks :), I need to calculate the swap usage on solaris server, please let me understand the output of below swap -s and swap -l commands. $swap -s total: 1774912k bytes allocated + 240616k reserved = 2015528k used, 14542512k available $swap -l swapfile dev swaplo... (6 Replies)
Discussion started by: seenuvasan1985
6 Replies
HK(4)							     Kernel Interfaces Manual							     HK(4)

NAME
hk - RK6-11/RK06 and RK07 moving head disk SYNOPSIS
/sys/conf/SYSTEM: NHK hk_drives # RK611, RK06/07 /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments hk ? 177440 210 5 hkintr # rk611/711 rk06/07 major device number(s): raw: 13 block: 4 minor device encoding: bits 0007 specify partition of HK drive bits 0070 specify HK drive DESCRIPTION
Files with minor device numbers 0 through 7 refer to various portions of drive 0; minor devices 8 through 15 refer to drive 1, etc. The standard device names begin with ``hk'' followed by the drive number and then a letter a-h for partitions 0-7 respectively. The character ? stands here for a drive number in the range 0-7. The block 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 files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word (even) boundary, and counts should be a multiple of 512 bytes (a disk sector). Likewise seek calls should specify a multiple of 512 bytes. DISK SUPPORT
The origin and size (in sectors) of the pseudo-disks on each drive are as follows: RK06 partitions: disk start length cyls comments hk?a 0 8316 0 - 125 root hk?b 8316 8316 126 - 251 swap hk?c 0 27126 0 - 410* whole pack plus badsect track hk?d unused hk?e unused hk?f unused hk?g 16632 10428 251 - 409 tmp hk?h 0 27060 0 - 409 whole pack minus badsect track RK07 partitions: disk start length cyls comments hk?a 0 8316 0 - 125 root hk?b 8316 8316 126 - 251 swap hk?c 0 53790 0 - 814* whole pack plus badsect track hk?d unused hk?e unused hk?f unused hk?g 16632 37092 252 - 813 hk?h 0 53724 0 - 814 whole pack minus badsect track Those partitions marked with an asterisk (``*'') allow access to bad block information stored at the end of some packs. Extreme care must be taken when creating file systems on these partitions to avoid overwriting any bad block information present. I general it's best to use newfs(8) to create file systems since it uses the ``safe'' partition sizes recored in /etc/disktab. FILES
/dev/hk[0-7][a-h] block files /dev/rhk[0-7][a-h] raw files /dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
ra(4), ram(4), rk(4), rl(4), rx(4), si(4), xp(4), dtab(5), autoconfig(8) DIAGNOSTICS
hk%d%c: hard error sn%d cs2=%b ds=%b er=%b. An unrecoverable error occurred during transfer of the specified sector of the specified disk partition. The contents of the cs2, ds and er registers are printed in octal and symbolically with bits decoded. The error was either unrecoverable, or a large number of retry attempts (including offset positioning and drive recalibration) could not recover the error. hk%d: write locked. The write protect switch was set on the drive when a write was attempted. The write operation is not recoverable. hk%d: not ready. The drive was spun down or off line when it was accessed. The i/o operation is not recoverable. hk%d: not ready (came back!). The drive was not ready, but after printing the message about being not ready (which takes a fraction of a second) was ready. The operation is recovered if no further errors occur. hk%d%c: soft ecc sn%d. A recoverable ECC error occurred on the specified sector of the specified disk partition. This happens normally a few times a week. If it happens more frequently than this the sectors where the errors are occuring should be checked to see if certain cylinders on the pack, spots on the carriage of the drive or heads are indicated. 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. DEC-standard error logging should be supported. A program to analyze the logged error information (even in its present reduced form) is needed. The partition tables for the file systems should be read off of each pack, as they are never quite what any single installation would pre- fer, and this would make packs more portable. 3rd Berkeley Distribution January 3, 1993 HK(4)
All times are GMT -4. The time now is 01:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy