Kbase 41518: Extent exceeds 2 GB file size limit - large file support capability
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P11518
FACT(s) (Environment):
Progress 9.1C
Progress 9.1D
SYMPTOM(s):
Extent exceeds 2 GB limit
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6091)
Offset in error 6091 is 2147467264.
bkxtn: write error, file <file-name> errno: <number>. (3646)
SYSTEM ERROR: File <file-name> too small <length>, blocksize <blocksize> extend failed." (4524)
Unable to extend data files enough to proceed. (6743)
SYSTEM ERROR: Attempted to exceed maximum size on file <pname>. (9452)
File system configured for Large File Support
CAUSE:
File size is near or over the 2 GB limit and could not be written to.
FIX:
The error messages indicate the file size is near or over the 2 GB limit and could not be written to.
In the case of version 9.1C or higher, this could mean:
1) Large file support was not enabled in Progress
2) File system was not created with large file support.
3) Operating System ulimit issue.
For an operating system to support large files, the file system must be created with large file support. This is done via an operating system administration utility or an option supplied to mkfs or crfs to include large file support. It generally can not be "turned on' after the file system has been created.
Progress Large File Support considerations:
-------------------------------------------
1) Large file support must be enabled at the file system level.
2) Users ulimit set large enough for you to create a file greater than 2 gig. Reference Solution P6261 for additional information on determining current ulimit.
note: Prior to repairing a database, it is strongly recommended that the
database be backed up.
If your file system accommodates large files, and ulimit is set appropriately, then all you need to do is to enable large file support in Progress.
Command: proutil dbname -C EnableLargeFiles (not case sensitive)
Once Large File Support is enabled, restart the database and it should proceed through crash recovery.