Bug 86268 - File package is not large-file capable
File package is not large-file capable
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: file (Show other bugs)
2.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-18 11:36 EST by Mike Gahagan
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-18 16:31:22 EST
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 Mike Gahagan 2003-03-18 11:36:31 EST
Description of problem:

/usr/bin/file is not capable of handling large files.

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

Red Hat Enterprise Linux AS (version 2.1)
file: 3.35-2 

(everything install with Q1 errata)


How reproducible:

always

Steps to Reproduce:
1.run /usr/bin/file on a file > 2GB
2.
3.
    
Actual results:

Can't stat 'filename' (Value too large for defined data type.)

Expected results:

Type of the file should be returned.

Additional info:

Works in 7.3 file version 3.37
Comment 1 Mike McLean 2003-03-18 16:31:22 EST
Works in file-3.39-8.7x
https://rhn.redhat.com/errata/RHSA-2003-087.html

Repeat after me...   :-)
  "I will up2date before I file a bug"
  "I will up2date before I file a bug"

.live.[root@i386-21as root]# stat huge
  File: "huge"
  Size: 4294967296      Blocks: 8396808    IO Block: -4612040817085771776
Regular FileDevice: 822h/2082d      Inode: 1081021     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: Tue Mar 18 16:11:09 2003
Modify: Tue Mar 18 16:10:38 2003
Change: Tue Mar 18 16:10:38 2003
 
.live.[root@i386-21as root]# file huge
huge: data
Comment 2 Mike Gahagan 2003-03-18 18:20:17 EST
oops :)

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