Sponsored Content
Operating Systems Linux Unable to remove file using rm: Disk space is full Post 302206661 by Pankajakshan on Wednesday 18th of June 2008 07:24:04 AM
Old 06-18-2008
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 `debug.out22621': No space left on device


Could you all help me out?


Thanks

Anoop
 

9 More Discussions You Might Find Interesting

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

2. Solaris

solaris 8 / disk space almost full

Hi All, My Solaris 8 firewall server is getting full on the / filesystem. I don't know which one should I delete. I think there's no more to delete on the file like logs or temp file. Does someone knows about deleting a safe file (or folder) on FS like /usr, /opt, /platform, /kernel, /sbin?... (7 Replies)
Discussion started by: itik
7 Replies

3. UNIX for Dummies Questions & Answers

how to install new packages when disk space is full

during installation i created four partitions mainly / 5GB /home 1GB /boot 100MB swap 2GB now since i didnt make the /usr partition all of the packages were being installed in the / partition ..now all the space in the / partition is filled ...i ran du -h... (3 Replies)
Discussion started by: tarunicon
3 Replies

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

5. UNIX for Advanced & Expert Users

Disk Space full

I was tryin to copy a large file under /tmp location. I guess the disk space got full and i got fork error. Then I tried removing some files but the shell did not let me do anything bash> rm apache22.tar bash: fork: Not enough space bash> pwd /tmp bash> vmstat 1 bash: fork: Not... (3 Replies)
Discussion started by: mohtashims
3 Replies

6. Shell Programming and Scripting

Unable to catch the redirection error when the disk is full

Hi Experts, Problem summary : I am facing the below problem on huge files when the disk is getting full on the half way through the execution. If the disk was already full , the commands fail & everything is fine. Sample Code : head_rec_data_file=`head -1 sample_file.txt` cat... (9 Replies)
Discussion started by: Pruthviraj_shiv
9 Replies

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

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

9. AIX

Unable to remove VIOS disk

Hello, I am unable to remove the disk, whenever i remove the disk using rmdev -dl hdisk2 or rmdev -Rdl hdisk2 the disk appears back when i run cfgmgr but unable to create any volume group on it # mkvg -y foovg hdisk2 0516-008 /usr/sbin/mkvg: LVM system call returned an unknown ... (20 Replies)
Discussion started by: filosophizer
20 Replies
CACHEFILESD.CONF(5)					       Cache Files Utilities					       CACHEFILESD.CONF(5)

NAME
/etc/cachefilesd.conf - Local file caching configuration file SYNOPSIS
The configuration file for cachefilesd which can manage a persistent cache for a variety of network filesystems using a set of files on an already mounted filesystem as the data store. DESCRIPTION
This configuration file can contain a number of commands. Each one should be on a separate line. Blank lines and lines beginning with a '#' character are considered to be comments and are discarded. The only mandatory command is: dir <path> This command specifies the directory containing the root of the cache. It may only specified once per configuration file. All the other commands are optional: brun <N>% bcull <N>% bstop <N>% frun <N>% fcull <N>% fstop <N>% These commands configure the culling limits. The defaults are 7% (run), 5% (cull) and 1% (stop) respectively. See the section on cache culling for more information. The commands beginning with a 'b' are file space (block) limits, those beginning with an 'f' are file count limits. tag <name> This command specifies a tag to FS-Cache to use in distinguishing multiple caches. This is only required if more than one cache is going to be used. The default is "CacheFiles". culltable <log2size> This command specifies the size of the tables holding the lists of cullable objects in the cache. The bigger the number, the faster and more smoothly that culling can proceed when there are many objects in the cache, but the more memory will be consumed by cachefilesd. The quantity is specified as log2 of the size actually required, for example 12 indicates a table of 4096 entries and 13 indicates 8192 entries. The permissible values are between 12 and 20, the latter indicating 1048576 entries. The default is 12. debug <mask> This command specifies a numeric bitmask to control debugging in the kernel module. The default is zero (all off). The following values can be OR'd into the mask to collect various information: 1 Turn on trace of function entry (_enter() macros) 2 Turn on trace of function exit (_leave() macros) 4 Turn on trace of internal debug points (_debug()) This mask can also be set through /sys/module/cachefiles/parameters/debug. EXAMPLES
As an example, consider the following: dir /var/fscache tag mycache brun 10% bcull 7% bstop 3% The places the cache storage objects in a directory called "/var/fscache", names the cache "mycache", permits the cache to run freely as long as there's at least 10% free space on /var/fscache/, starts culling the cache when the free space drops below 7% and stops writing new stuff into the cache if the amount of free space drops below 3%. If the cache is suspended, it won't reactivate until the amount of free space rises again to 10% or better. CACHE CULLING
The cache may need culling occasionally to make space. This involves discarding objects from the cache that have been used less recently than anything else. Culling is based on the access time of data objects. Empty directories are culled if not in use. Cache culling is done on the basis of the percentage of blocks and the percentage of files available in the underlying filesystem. There are six "limits": brun frun If the amount of free space and the number of available files in the cache rises above both these limits, then culling is turned off. bcull fcull If the amount of available space or the number of available files in the cache falls below either of these limits, then culling is started. bstop fstop If the amount of available space or the number of available files in the cache falls below either of these limits, then no further allocation of disk space or files is permitted until culling has raised things above these limits again. These must be configured thusly: 0 <= bstop < bcull < brun < 100 0 <= fstop < fcull < frun < 100 Note that these are percentages of available space and available files, and do not appear as 100 minus the percentage displayed by the df program. The userspace daemon scans the cache to build up a table of cullable objects. These are then culled in least recently used order. A new scan of the cache is started as soon as space is made in the table. Objects will be skipped if their atimes have changed or if the kernel module says it is still using them. SEE ALSO
cachefilesd(8), df(1), /usr/share/doc/cachefilesd-*/README AUTHORS
The cachefilesd software has been developed by David Howells Linux 14 November 2005 CACHEFILESD.CONF(5)
All times are GMT -4. The time now is 07:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy