Bug 158668 - php not capable of opening >2Gb files
php not capable of opening >2Gb files
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
4
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-24 14:31 EDT by Alberto de Luis
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-21 11:37:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alberto de Luis 2005-05-24 14:31:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4

Description of problem:
This is a petition for a default php.rpm with big files opening posibility. When I try to fopen a file exceding 2GB php returns this error:

PHP Warning:  fopen(file:///data/fasta/homo_sapiens_core_31_35d.dna.fa): failed to open stream: File too large in /data/www/html/probefinder/scripts/fastasha1.php on line 5

Is possible to surpass this limit in the future?

Thank you!

Version-Release number of selected component (if applicable):
php-5.0.4-10

How reproducible:
Always

Steps to Reproduce:
1. Prepare a big file (>2GB)
2. Try to open (fopen($file);)
  

Actual Results:  Scripts return an error, for example:

PHP Warning:  fopen(file:///data/fasta/homo_sapiens_core_31_35d.dna.fa): failed to open stream: File too large in /data/www/html/probefinder/scripts/fastasha1.php on line 5

Expected Results:  Script reading the file.

Additional info:
Comment 1 Joe Orton 2005-06-21 11:37:40 EDT
There is no easy fix for this, unfortunately; it requires fixing properly
upstream and is likely to require interface changes.

Note You need to log in before you can comment on or make changes to this bug.