Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 198654

Summary:	find missing Large File Support
Product:	Red Hat Enterprise Linux 4	Reporter:	Bastien Nocera <bnocera>
Component:	findutils	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED ERRATA	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	benl, tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2006-0679	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-09-27 06:35:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	201655

Description Bastien Nocera 2006-07-12 15:17:12 UTC

findutils-4.1.20-7

Microsoft NFS servers are known to create very high inode numbers in their
stat() output (see bug #163365 for example)

When running find on such a server, one would get the error:
Value too large for defined data type

Doing this change (tested by Hideshi Fuchi <hfuchi>):
-%define        optflags $RPM_OPT_FLAGS -D_GNU_SOURCE
+%define        optflags $RPM_OPT_FLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
to the spec file fixes the problem.

Comment 1 Miloslav Trmač 2006-07-15 20:07:17 UTC

Looks fine.

(The -D_FILE_OFFSET_BITS=64 is necessary even though the top-level configure
sets up _FILE_OFFSET_BITS because the included gnulib has its own configure script.)

Comment 18 Red Hat Bugzilla 2006-09-27 06:35:44 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0679.html