Unable to remove file using rm: Disk space is full Post: 302206671

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

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

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

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

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

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

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

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

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

LEARN ABOUT OPENDARWIN

clri

CLRI(8) 						    BSD System Manager's Manual 						   CLRI(8)

NAME

     clri -- clear an inode

SYNOPSIS

     clri special_device inode_number ...

DESCRIPTION

     Clri is obsoleted for normal file system repair work by fsck(8).

     Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device.  The fsck(8) utility is
     usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s).  Both read and write permission
     are required on the specified special_device.

     The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8).  Once removed, it is
     anticipated that fsck(8) will be able to clean up the resulting mess.

SEE ALSO

     fsck(8), fsdb(8), icheck(8), ncheck(8)

BUGS

     If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache.

4th Berkeley Distribution					  April 19, 1994					 4th Berkeley Distribution