Kbase P37686: What does the error "Insufficient disk space or Write access denied" really mean ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/15/2008 |
|
Status: Verified
GOAL:
What does the error "Insufficient disk space or Write access denied" really mean ?
GOAL:
Guidelines for troubleshooting error 291
GOAL:
Insufficient disk space or Write access denied (291)
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
The Progress (291) error says:
Insufficient disk space or Write access denied
In fact, a (291) error can be caused by insufficient disk space but it can also be caused by anything that prevents disk reads and writes such as:
1. Physical read error or write error on the disk itself
2. A network problem (if trying to access a disk on a network)
3. A file permissions problem
4. A file not shared properly and some other person or process
has it locked up at this moment
5. Not enough file handles (this is a common problem in UNIX,
MS-DOS and Windows 3.1/3.11 but not in Windows 95/98 or NT).
As an example, one obvious reason for 291 on UNIX could be
the -T parameter used with /tmp directory; ie. -T /tmp
Now when /tmp directory gets filled up, 291 occurs
6. Hardware problem
7. Insufficient disk space if the file to save is bigger than the space
available (for example a big temporary sort file).
The (291) is a "pass through error message." That is, all the text the left of the (291) was generated by the operating system and then delivered to Progress. Progress then displays the words from the operating system and appends the "(291)" onto the right side of the error message. To find the true cause of the error message, you need to look up the error text and operating system error number (if any) in the operating system's manuals.
1. A simple possibility to test the disk physically is by copying, modifying and saving files. The test files should have at least the same size as those
for which you get error (291).
2. Same as 1. applies if the disk is on the network.
3. On Unix use ls -lisa on Windows use the Windows Explorer -> right click on
the folder or file -> Properties -> Security -> Permissions to check the
file permissions
4. A file size of 0 indicates that the file is in use by an other user.
You will get an operating system error if you try to move a file in use.
5. Check with the command ulimit -Sa and ulimit -Ha the available file handles
on Unix. Empty your /tmp by rebooting or by using rm on Unix regularly.
6. Use Operating system utilities to check the hardware e.g. chkdsk on Windows.
7. Use df on Unix or on Windows use the Windows Explorer -> right click on
the folder or file -> Properties -> General to check if enough disk space
is available.
Correct problems encountered appropriate.