swapon.2 (2010 09)

swapon(2) swapon(2)

(TO BE OBSOLETED)

[EALREADY] The device associated with path already has swap turned on.

[EBUSY] The device associated with path is already in use.

[EEXIST] The device associated with path was speciﬁed at system conﬁguration time to add

swap at a speciﬁed location, but that location is within an existing ﬁle system on the

device.

[EFAULT] The LIF header on the device associated with path contains inconsistent directory

data.

[EIO] Unable to read the device associated with path .

[ELOOP] Too many symbolic links were encountered in translating the path name.

[ENAMETOOLONG]

The length of the speciﬁed path name exceeds

PATH_MAX bytes, or the length of a

component of the path name exceeds

NAME_MAX bytes while

_POSIX_NO_TRUNC

is in effect.

[ENODEV] The device associated with path does not exist.

[ENOENT] The system-imposed limit on the number of swap ﬁle entries has been reached.

[ENOSPC] There is is not enough available space on the speciﬁed ﬁle system or device.

[ENOSYS] The device associated with path was speciﬁed at system conﬁguration time to add

swap following the ﬁle system, but no ﬁle system was found.

[ENOTBLK] The path argument is not a block special ﬁle or the root directory of a ﬁle system.

[ENOTDIR] A component of the path is not a directory.

[ENXIO] The device associated with path could not be opened.

[EPERM] The effective user ID is not a user with appropriate privileges.

[EROFS] The device associated with path is read-only.

WARNINGS

On systems running VxVM 3.5, the swap volumes to be conﬁgured for system crash dumps should be

created with the usage type as

swap during the creation of the swap volume. Not doing so will cause a

dump corruption. You could use the -U option of vxassist to do the same.

No means is available to stop swapping to a device.

The system allocates no less than the amount speciﬁed in min. However, to make the most efﬁcient use

of space, more than the amount requested might be taken from the ﬁle system. The actual amount taken

will not exceed the number of ﬁle system blocks indicated in reserve .

Swapping to a ﬁle system is usually slower than swapping to a device.

Once ﬁle system blocks have been allocated for swap space, the ﬁle system can not be unmounted unless

the system is rebooted.

swapctl() is the replacement for swapon(). swapon() is to be obsoleted at a future date.

AUTHOR

swapon() was developed by the University of California, Berkeley.