Sponsored Content
Full Discussion: Directory full error
Top Forums UNIX for Dummies Questions & Answers Directory full error Post 302882653 by bakunin on Wednesday 8th of January 2014 11:29:12 AM
Old 01-08-2014
Please cut output and post it enclosed in CODE-tags. Not everybody is willing to wade through a huge XML-file just to see the one-line error message.

In fact the error is "/ace is 97 % full" and "/ace" is most probably a filesystem. Check it like this (your output might look somewhat different):

Code:
# mount
  node       mounted        mounted over    vfs       date        options      
-------- ---------------  ---------------  ------ ------------ --------------- 
         /dev/hd4         /                jfs2   Nov 18 17:22 rw,log=/dev/hd8 
         /dev/hd2         /usr             jfs2   Nov 18 17:22 rw,log=/dev/hd8 
         /dev/hd9var      /var             jfs2   Nov 18 17:22 rw,log=/dev/hd8 
         /dev/hd3         /tmp             jfs2   Nov 18 17:22 rw,log=/dev/hd8

and if there is a line with "/ace" it is a filesystem.

Why you could delete two files and still see this warning is because of a common gotcha every novice SysAdmin falls for sooner or later: as long as a process has opened a file it is not unlinked (its space reclaimed) by the system, even if it is deleted. So most probably there is a process (or several processes) writing to the files you deleted. Until this process releases the file (i.e. via ending, closing the file, etc.) it is still there, even if its directory entry is already removed because you deleted it.

What you can do is: identify the process(es) and stop them. This will immediately unlink the file and the space it takes will be available again as free. Another option (which essentially does the same) is to reboot the system. The third option is to enlarge the filesystem. Depending on your system this could be possible without unmounting the FS.

To avoid creating the same problem again you should always check if a process accesses a file before you delete it. For this there are several tools, "fuser" is probably the most wide-known.

If a process uses a file you need to make smaller, instead of deleteing it you should shorten it:
Code:
# cat /dev/null > /file/in/question

will reduce it to length zero without interrupting the process writing to it.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Savecore directory is full, what can be done?

what should i do in this situation. the system crashes and when it rebooted, it tries to dump the core files in the savecore directory. it finds that there is not enough space to dump the files so it just goes ahead and boots up and saves as much core as the directory can withhold 1. now my... (1 Reply)
Discussion started by: TRUEST
1 Replies

2. Solaris

/ directory is 100% full

Dear experts My / directory shows 100% full. What should I do??? What is normal size and how can I prevent it. I am using Solaris 8 on an Ultra 60. Thanks for your advises. Reza (6 Replies)
Discussion started by: Reza Nazarian
6 Replies

3. UNIX for Dummies Questions & Answers

Full Directory Listing...

Is there a way of listing everything under a directory. So for example if you wanted to know everything under the USR directory you would get all the sub directories and files in those directories as well as the file directly under the USR directory. I would imagine that you could do this... (5 Replies)
Discussion started by: B14speedfreak
5 Replies

4. Solaris

Full Directory without data....

$ df -hl Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 5.0G 4.7G 52% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K ... (2 Replies)
Discussion started by: adel8483
2 Replies

5. HP-UX

directory full?

I'm not a unix admin, just fell into support, so I may be asking a real duh question. Client runs a PeopleSoft HR/Payrool system. The batch server runs in HPUX PA_RISC 11.11 When a batch process runs, output is written to "staging" directory. When the job finishes, successfully or not, the... (1 Reply)
Discussion started by: abNORMal
1 Replies

6. Solaris

root directory is full

root directory in server / is full 100% , i already tried to delete any core file , log , .. still files under /proc directory take more than 4 G.. what you advice please i don't want to format the server and install again and re partition , i tried the FORMAT tools ! but it seems i cant do... (5 Replies)
Discussion started by: moata_u
5 Replies

7. AIX

\tmp Directory is full up to 99%.

Dear All, We are on AIX OS, /tmp directory is filled up to 99% percent, Please suggest, How to get free space for "/tmp"? which files can be deleted from /tmp? and How to delete it? is there any commands..... Thanks in advance, Its very urgent, Helpful answers will be appreciated, Please... (7 Replies)
Discussion started by: kak
7 Replies

8. Shell Programming and Scripting

How do I get an ls -l to not show the full directory path?

Hey I'm new to the forums here, and I'm seeking help for this script that I'm writing. When I do ls -l of a directory it shows the full pathname for files in it. For example, if the directory is /internet/post/forum/ and the file is topic, it currently shows internet/post/forum/topic. What's the... (3 Replies)
Discussion started by: unity04
3 Replies

9. UNIX for Dummies Questions & Answers

Extract directory from full file name?

I think I know what this is doing, but the 'eval' is confusing fname=$(echo ${lineItem} | awk 'BEGIN {FS=";"}{print $1}') fname=${fname%%+(])} fname=${fname##+(])} eval "fname=${fname}" The first line extracts the contents of the line preceeding the ";" 2nd & 3rd lines trim the value (I... (5 Replies)
Discussion started by: jdorn001
5 Replies

10. UNIX for Dummies Questions & Answers

Extract directory name from the full directory path in UNIX using shell scripting

My input is as below : /splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt /splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt /splunk/scrubbed/loyal/IFIND.HELLO.WROC.txt /splunk/scrubbed/triumph/ifind.triumph.txt From the above input I want to extract the file names only . Basically I want to... (5 Replies)
Discussion started by: IshuGupta
5 Replies
Gnome2::VFS::Directory(3pm)				User Contributed Perl Documentation			       Gnome2::VFS::Directory(3pm)

NAME
Gnome2::VFS::Directory - represents a directory METHODS
list = Gnome2::VFS::Directory->list_load ($text_uri, $options) o $text_uri (string) o $options (Gnome2::VFS::FileInfoOptions) Returns a GnomeVFSResult and the GnomeVFSFileInfo's corresponding to the directory's content. list = Gnome2::VFS::Directory->open ($text_uri, $options) o $text_uri (string) o $options (Gnome2::VFS::FileInfoOptions) Returns a GnomeVFSResult and a GnomeVFSDirectoryHandle. list = Gnome2::VFS::Directory->open_from_uri ($uri, $options) o $uri (Gnome2::VFS::URI) o $options (Gnome2::VFS::FileInfoOptions) Returns a GnomeVFSResult and a GnomeVFSDirectoryHandle. result = Gnome2::VFS::Directory->visit ($uri, $info_options, $visit_options, $func, $data=undef) o $uri (string) o $info_options (Gnome2::VFS::FileInfoOptions) o $visit_options (Gnome2::VFS::DirectoryVisitOptions) o $func (scalar) o $data (scalar) result = Gnome2::VFS::Directory->visit_files ($text_uri, $file_ref, $info_options, $visit_options, $func, $data=undef) o $text_uri (string) o $file_ref (scalar) o $info_options (Gnome2::VFS::FileInfoOptions) o $visit_options (Gnome2::VFS::DirectoryVisitOptions) o $func (scalar) o $data (scalar) result = Gnome2::VFS::Directory->visit_files_at_uri ($uri, $file_ref, $info_options, $visit_options, $func, $data=undef) o $uri (Gnome2::VFS::URI) o $file_ref (scalar) o $info_options (Gnome2::VFS::FileInfoOptions) o $visit_options (Gnome2::VFS::DirectoryVisitOptions) o $func (scalar) o $data (scalar) result = Gnome2::VFS::Directory->visit_uri ($uri, $info_options, $visit_options, $func, $data=undef) o $uri (Gnome2::VFS::URI) o $info_options (Gnome2::VFS::FileInfoOptions) o $visit_options (Gnome2::VFS::DirectoryVisitOptions) o $func (scalar) o $data (scalar) ENUMS AND FLAGS
flags Gnome2::VFS::DirectoryVisitOptions o 'default' / 'GNOME_VFS_DIRECTORY_VISIT_DEFAULT' o 'samefs' / 'GNOME_VFS_DIRECTORY_VISIT_SAMEFS' o 'loopcheck' / 'GNOME_VFS_DIRECTORY_VISIT_LOOPCHECK' o 'ignore-recurse-error' / 'GNOME_VFS_DIRECTORY_VISIT_IGNORE_RECURSE_ERROR' flags Gnome2::VFS::FileInfoOptions o 'default' / 'GNOME_VFS_FILE_INFO_DEFAULT' o 'get-mime-type' / 'GNOME_VFS_FILE_INFO_GET_MIME_TYPE' o 'force-fast-mime-type' / 'GNOME_VFS_FILE_INFO_FORCE_FAST_MIME_TYPE' o 'force-slow-mime-type' / 'GNOME_VFS_FILE_INFO_FORCE_SLOW_MIME_TYPE' o 'follow-links' / 'GNOME_VFS_FILE_INFO_FOLLOW_LINKS' o 'get-access-rights' / 'GNOME_VFS_FILE_INFO_GET_ACCESS_RIGHTS' o 'name-only' / 'GNOME_VFS_FILE_INFO_NAME_ONLY' o 'get-acl' / 'GNOME_VFS_FILE_INFO_GET_ACL' o 'get-selinux-context' / 'GNOME_VFS_FILE_INFO_GET_SELINUX_CONTEXT' enum Gnome2::VFS::Result o 'ok' / 'GNOME_VFS_OK' o 'error-not-found' / 'GNOME_VFS_ERROR_NOT_FOUND' o 'error-generic' / 'GNOME_VFS_ERROR_GENERIC' o 'error-internal' / 'GNOME_VFS_ERROR_INTERNAL' o 'error-bad-parameters' / 'GNOME_VFS_ERROR_BAD_PARAMETERS' o 'error-not-supported' / 'GNOME_VFS_ERROR_NOT_SUPPORTED' o 'error-io' / 'GNOME_VFS_ERROR_IO' o 'error-corrupted-data' / 'GNOME_VFS_ERROR_CORRUPTED_DATA' o 'error-wrong-format' / 'GNOME_VFS_ERROR_WRONG_FORMAT' o 'error-bad-file' / 'GNOME_VFS_ERROR_BAD_FILE' o 'error-too-big' / 'GNOME_VFS_ERROR_TOO_BIG' o 'error-no-space' / 'GNOME_VFS_ERROR_NO_SPACE' o 'error-read-only' / 'GNOME_VFS_ERROR_READ_ONLY' o 'error-invalid-uri' / 'GNOME_VFS_ERROR_INVALID_URI' o 'error-not-open' / 'GNOME_VFS_ERROR_NOT_OPEN' o 'error-invalid-open-mode' / 'GNOME_VFS_ERROR_INVALID_OPEN_MODE' o 'error-access-denied' / 'GNOME_VFS_ERROR_ACCESS_DENIED' o 'error-too-many-open-files' / 'GNOME_VFS_ERROR_TOO_MANY_OPEN_FILES' o 'error-eof' / 'GNOME_VFS_ERROR_EOF' o 'error-not-a-directory' / 'GNOME_VFS_ERROR_NOT_A_DIRECTORY' o 'error-in-progress' / 'GNOME_VFS_ERROR_IN_PROGRESS' o 'error-interrupted' / 'GNOME_VFS_ERROR_INTERRUPTED' o 'error-file-exists' / 'GNOME_VFS_ERROR_FILE_EXISTS' o 'error-loop' / 'GNOME_VFS_ERROR_LOOP' o 'error-not-permitted' / 'GNOME_VFS_ERROR_NOT_PERMITTED' o 'error-is-directory' / 'GNOME_VFS_ERROR_IS_DIRECTORY' o 'error-no-memory' / 'GNOME_VFS_ERROR_NO_MEMORY' o 'error-host-not-found' / 'GNOME_VFS_ERROR_HOST_NOT_FOUND' o 'error-invalid-host-name' / 'GNOME_VFS_ERROR_INVALID_HOST_NAME' o 'error-host-has-no-address' / 'GNOME_VFS_ERROR_HOST_HAS_NO_ADDRESS' o 'error-login-failed' / 'GNOME_VFS_ERROR_LOGIN_FAILED' o 'error-cancelled' / 'GNOME_VFS_ERROR_CANCELLED' o 'error-directory-busy' / 'GNOME_VFS_ERROR_DIRECTORY_BUSY' o 'error-directory-not-empty' / 'GNOME_VFS_ERROR_DIRECTORY_NOT_EMPTY' o 'error-too-many-links' / 'GNOME_VFS_ERROR_TOO_MANY_LINKS' o 'error-read-only-file-system' / 'GNOME_VFS_ERROR_READ_ONLY_FILE_SYSTEM' o 'error-not-same-file-system' / 'GNOME_VFS_ERROR_NOT_SAME_FILE_SYSTEM' o 'error-name-too-long' / 'GNOME_VFS_ERROR_NAME_TOO_LONG' o 'error-service-not-available' / 'GNOME_VFS_ERROR_SERVICE_NOT_AVAILABLE' o 'error-service-obsolete' / 'GNOME_VFS_ERROR_SERVICE_OBSOLETE' o 'error-protocol-error' / 'GNOME_VFS_ERROR_PROTOCOL_ERROR' o 'error-no-master-browser' / 'GNOME_VFS_ERROR_NO_MASTER_BROWSER' o 'error-no-default' / 'GNOME_VFS_ERROR_NO_DEFAULT' o 'error-no-handler' / 'GNOME_VFS_ERROR_NO_HANDLER' o 'error-parse' / 'GNOME_VFS_ERROR_PARSE' o 'error-launch' / 'GNOME_VFS_ERROR_LAUNCH' o 'error-timeout' / 'GNOME_VFS_ERROR_TIMEOUT' o 'error-nameserver' / 'GNOME_VFS_ERROR_NAMESERVER' o 'error-locked' / 'GNOME_VFS_ERROR_LOCKED' o 'error-deprecated-function' / 'GNOME_VFS_ERROR_DEPRECATED_FUNCTION' o 'error-invalid-filename' / 'GNOME_VFS_ERROR_INVALID_FILENAME' o 'error-not-a-symbolic-link' / 'GNOME_VFS_ERROR_NOT_A_SYMBOLIC_LINK' o 'num-errors' / 'GNOME_VFS_NUM_ERRORS' SEE ALSO
Gnome2::VFS COPYRIGHT
Copyright (C) 2003-2007 by the gtk2-perl team. This software is licensed under the LGPL. See Gnome2::VFS for a full notice. perl v5.14.2 2011-11-15 Gnome2::VFS::Directory(3pm)
All times are GMT -4. The time now is 03:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy