Unable to add space


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Unable to add space
Prev   Next
# 5  
Old 05-27-2016
Yes, I didn't spot that. Apologies.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

Unable to get full FS space after mounting

Hi, I am unable to get the full FS space, as /home is 100% utilized and after deleting unwanted files, its still 100%. After checking the du -sk * | sort -n output and converting it to MBs, the total sizes comes out to be 351 MBs only however the lvol is of 3GB. I don't know where is all the space... (2 Replies)
Discussion started by: Kits
2 Replies

2. Solaris

Unable to find utilized disk space on zone server.

Hi, I am unable to find remaining space on solaris 10. below is output. I am facing this issue on zone server. bash-3.00# df -h / Filesystem size used avail capacity Mounted on / 59G 59G 0K 100% / bash-3.00# pwd / bash-3.00# du -sh * 1K File_Stores 19K TT_DB 9K app 1K bin... (4 Replies)
Discussion started by: manoj.solaris
4 Replies

3. AIX

F7fa22c9 i o sysj2 unable to allocate space in file system

F7FA22C9 I O SYSJ2 UNABLE TO ALLOCATE SPACE IN FILE SYSTEM edit by bakunin: until you are willing to phrase a decent question i am unwilling to tolerate such a spammed thread here. - Thread closed - (0 Replies)
Discussion started by: ranjithm
0 Replies

4. Shell Programming and Scripting

Unable to read the first space of a record in while loop

I have a loop like while read i do echo "$i" . . . done < tms.txt The tms.txt contians data like 2008-02-03 00:00:00 <space>00:00:00 . . . 2010-02-03 10:54:32 (2 Replies)
Discussion started by: machomaddy
2 Replies

5. Red Hat

Unable to free space due to inode in use by database

Hi, I am having similar issue showing filesystem 100% even after deleting the files. I understood the issue after going through this chain. But i can not restart the processes being oracle database. Is there way like mounting filesytem with specific options would avoid happening this issue. How... (0 Replies)
Discussion started by: prashant185
0 Replies

6. Solaris

Solaris file system unable to use available space

Hi, The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB. The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space. ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies

7. Solaris

Unable to understand disk layout and where are the free space

Hi I am unable to understand the disk layout of one of my disk attached to v240. This is newly installed system from jumpstart. I am unable to see the free space on backup slice 2 and there are 0 to 8 slices listed when I run format and print the disk info, also there is no reference of... (9 Replies)
Discussion started by: kumarmani
9 Replies

8. Solaris

[Sol10/VMWare] Unable to see new disk space.

The master copy was set to 5 gigs. As the instance is cloned, additional space is provided. I was given a new instance along with 15 gigs of additional space. The problem is I can't see the additional space, either as additional space on the primary disk or as a second disk. # format Searching... (8 Replies)
Discussion started by: BOFH
8 Replies

9. Linux

Unable to remove file using rm: Disk space is full

Hi all, My disk space is 100% full. df -k <dir> -> 100% One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs. However i'm unable to remove the file giving out the following error message: rm -f debug.out22621 rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies

10. SCO

Unable to dump due to limited space?

After rebuilding the RAIDs on the SCO Unix, the following dialog appears when rebooting the machine. Fssat: /dev/boot mounted Mounted /stand filesystem Fsstat: /dev/usr1 okay Mounted /usr1 filesystem (continues usr2, usr3, Fsstat: /dev/usr4 okay Panic: HTFS: Bad directory ino... (2 Replies)
Discussion started by: Mac Tire
2 Replies
Login or Register to Ask a Question
swapon(2)							System Calls Manual							 swapon(2)

NAME
swapon() - add swap space for interleaved paging and swapping SYNOPSIS
Remarks The ANSI C "" construct denotes a variable length argument list whose optional and required members are given in the associated comment DESCRIPTION
The system call makes a block device or a directory named path available to the system for paging and swapping. priority indicates the order in which the swap space from the device or file system is used. It has a range of 0 (highest) to 10 (lowest). Space is taken from the lower-numbered systems first. can be used only by users who have appropriate privileges. If path names a block device file makes it available to the system at the specified priority for allocation for paging and swapping. In this form, takes only two arguments: the path to the block device file, and the priority. The device associated with path can be a device already known to the system, defined at system configuration time, or it can be a previ- ously unspecified device. If the device was already defined at system configuration time and also has a start and/or size defined for that swap device, these values are used. Otherwise, if a filesystem exists on the device, swap is added following the filesystem, or if no filesystem exists, the complete device is used for swap. See the appropriate system administrator's manual for information on how the size of the swap area is calculated. If path names a directory makes the blocks on the file system rooted at path available for paging and swapping. The min, limit, and reserve arguments are passed and used only if the path argument names a directory. min indicates the number of file system blocks to take from the file system when is called. limit indicates the maximum number of file system blocks the swap system is allowed to take from the file system. reserve indicates the number of file system blocks that are saved for file system use only. For a pre-existing directory swap, a value of -1 for min, limit, reserve, or priority will keep the value unchanged. This can be used to change selective values without affecting others. For example, if priority of a pre-existing directory swap needs to be changed without affecting the values of min, limit, or reserve, one can specify the new priority value and pass -1 for other arguments. The size for the file system blocks mentioned above is the preferred file system block size. The preferred file system block size can be obtained by the call. The value of min, limit, or reserve is rounded up to the tunable size. ERRORS
If fails, is set to one of the following values. A component of the path prefix denies search permission. One of priority, min, limit, or reserve arguments is invalid. The device associated with path already has swap turned on. The device associated with path is already in use. The device associated with path was specified at system configuration time to add swap at a specified location, but that location is within an existing file system on the device. The LIF header on the device associated with path contains inconsistent directory data. Unable to read the device associated with path. Too many symbolic links were encountered in translating the path name. The length of the specified path name exceeds bytes, or the length of a component of the path name exceeds bytes while is in effect. The device associated with path does not exist. The system-imposed limit on the number of swap file entries has been reached. There is is not enough available space on the specified file system or device. The device associated with path was specified at system configuration time to add swap following the file system, but no file system was found. The path argument is not a block special file or the root directory of a file system. A component of the path is not a directory. The device associated with path could not be opened. The effective user ID is not a user with appropriate privileges. The device associated with path is read-only. WARNINGS
On systems running VxVM 3.5, the swap volumes to be configured for system crash dumps should be created with the usage type as during the creation of the swap volume. Not doing so will cause a dump corruption. You could use the option of to do the same. No means is available to stop swapping to a device. The system allocates no less than the amount specified in min. However, to make the most efficient use of space, more than the amount requested might be taken from the file system. The actual amount taken will not exceed the number of file system blocks indicated in reserve. Swapping to a file system is usually slower than swapping to a device. Once file system blocks have been allocated for swap space, the file system can not be unmounted unless the system is rebooted. is the replacement for is to be obsoleted at a future date. AUTHOR
was developed by the University of California, Berkeley. SEE ALSO
swapon(1M), vxassist(1M), swapctl(2), privileges(5). TO BE OBSOLETED swapon(2)