Sponsored Content
Operating Systems Solaris /tmp: File system full, swap space limit exceeded Post 302111050 by frustrated1 on Sunday 18th of March 2007 03:56:08 PM
Old 03-18-2007
ok, fair point.

Can I change it so that filling /tmp doesnt kill swap and therefore my server?
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

file system is full : But df -k shows space available

Dear Experts, We are using Digital Unix 4.0d on Alpha DS-20 E. /var/adm/messages showed the following error Jul 24 19:58:37 cbehotbill2 vmunix: /BSCSprod: write failed, file system is full Jul 24 19:58:38 cbehotbill2 last message repeated 2 times But df -k showed BSCS_dmn#BSCSprod ... (4 Replies)
Discussion started by: geraldwilson
4 Replies

2. Programming

File size limit exceeded

When i run my C program which dynamically creates the output file, the program stops after sometime and gives the error "File size limit exceeded" even though my working directory has space.Can anyone plz help me out. (13 Replies)
Discussion started by: drshah
13 Replies

3. Solaris

Increase size of /tmp swap File

Hi Guys I need to increase the size of my /tmp swap file. What is the easiest way to do this. Thanks Carson (2 Replies)
Discussion started by: cmackin
2 Replies

4. UNIX for Dummies Questions & Answers

File size limit exceeded... SCO ulimit?

Hello - O/S is UnixWare 7.1.4 My prefered method of copying files between servers is 'rcp', which does not recognize symbolic links; therefore, files are duplicated many times over. To avoid this duplication, I would like to use 'tar' and/or 'cpio' and pipe them through 'rcp', but... (1 Reply)
Discussion started by: rm -r *
1 Replies

5. 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

6. AIX

/tmp file system full

Hi, I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized. Regards, Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies

7. Solaris

Solaris full /tmp - du and df different swap NOT filled

Hello all, The issue is # df -h /tmp Filesystem size used avail capacity Mounted on swap 4.0G 4.0G 8.7M 100% /tmp # du -sh /tmp/ 87M /tmp By now you probably will say that this is open file destriptor issue. Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies

8. 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

9. Solaris

File system full - not removed: No space left on device

Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow: not removed: No space left on device Any help would be very much appreciated. (10 Replies)
Discussion started by: craigsky
10 Replies

10. Emergency UNIX and Linux Support

Swap space (almost) full

Hello, This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot. # top top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18 Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
SYSTEMD.SWAP(5) 						   systemd.swap 						   SYSTEMD.SWAP(5)

NAME
systemd.swap - Swap unit configuration SYNOPSIS
swap.swap DESCRIPTION
A unit configuration file whose name ends in ".swap" encodes information about a swap device or file for memory paging controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The swap specific configuration options are configured in the [Swap] section. Additional options are listed in systemd.exec(5), which define the execution environment the swapon(8) program is executed in, in systemd.kill(5), which define the way these processes are terminated, and in systemd.resource-control(5), which configure resource control settings for these processes of the unit. Swap units must be named after the devices or files they control. Example: the swap device /dev/sda5 must be configured in a unit file dev-sda5.swap. For details about the escaping logic used to convert a file system path to a unit name, see systemd.unit(5). Note that swap units cannot be templated, nor is possible to add multiple names to a swap unit by creating additional symlinks to it. IMPLICIT DEPENDENCIES
The following dependencies are implicitly added: o All swap units automatically get the BindsTo= and After= dependencies on the device units or the mount units of the files they are activated from. Additional implicit dependencies may be added as result of execution and resource control parameters as documented in systemd.exec(5) and systemd.resource-control(5). DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set: o Swap units automatically acquire a Conflicts= and a Before= dependency on umount.target so that they are deactivated at shutdown as well as a Before=swap.target dependency. FSTAB
Swap units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Swaps listed in /etc/fstab will be converted into native units dynamically at boot and when the configuration of the system manager is reloaded. See systemd-fstab- generator(8) for details about the conversion. If a swap device or file is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence. When reading /etc/fstab, a few special options are understood by systemd which influence how dependencies are created for swap units. noauto, auto With noauto, the swap unit will not be added as a dependency for swap.target. This means that it will not be activated automatically during boot, unless it is pulled in by some other unit. The auto option has the opposite meaning and is the default. nofail With nofail, the swap unit will be only wanted, not required by swap.target. This means that the boot will continue even if this swap device is not activated successfully. OPTIONS
Swap files must include a [Swap] section, which carries information about the swap device it supervises. A number of options that may be used in this section are shared with other unit types. These options are documented in systemd.exec(5) and systemd.kill(5). The options specific to the [Swap] section of swap units are the following: What= Takes an absolute path of a device node or file to use for paging. See swapon(8) for details. If this refers to a device node, a dependency on the respective device unit is automatically created. (See systemd.device(5) for more information.) If this refers to a file, a dependency on the respective mount unit is automatically created. (See systemd.mount(5) for more information.) This option is mandatory. Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as "%%". Priority= Swap priority to use when activating the swap device or file. This takes an integer. This setting is optional and ignored when the priority is set by pri= in the Options= key. Options= May contain an option string for the swap device. This may be used for controlling discard options among other functionality, if the swap backing device supports the discard or trim operation. (See swapon(8) for more information.) Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as "%%". TimeoutSec= Configures the time to wait for the swapon command to finish. If a command does not exit within the configured time, the swap will be considered failed and be shut down again. All commands still running will be terminated forcibly via SIGTERM, and after another delay of this time with SIGKILL. (See KillMode= in systemd.kill(5).) Takes a unit-less value in seconds, or a time span value such as "5min 20s". Pass "0" to disable the timeout logic. Defaults to DefaultTimeoutStartSec= from the manager configuration file (see systemd- system.conf(5)). Check systemd.exec(5) and systemd.kill(5) for more settings. SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.exec(5), systemd.kill(5), systemd.resource-control(5), systemd.device(5), systemd.mount(5), swapon(8), systemd-fstab-generator(8), systemd.directives(7) systemd 237 SYSTEMD.SWAP(5)
All times are GMT -4. The time now is 08:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy