Bug 113150

Summary: mkfs.ext3 with -T largefile gets Floating point exception
Product: [Fedora] Fedora Reporter: Gregory Gulik <greg>
Component: e2fsprogsAssignee: Florian La Roche <laroche>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-12 13:01:42 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:

Description Gregory Gulik 2004-01-08 22:13:18 UTC 
Description of problem:

Attempting to create a file system on a large drive with a lrage block
size causes newfs.ext3 to fail with a Floating point exception.
I've tried both -T largefile4  and -T largefile and both result in the
failure.  It works fine if you leave off the -T option.

The drive in question is in a 200G drive in a USB 2.0 enclosure.
The same thing happens with a 250G drive in the same enclosure.

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

mke2fs 1.34 (25-Jul-2003)

How reproducible:

Always.

Steps to Reproduce:
1. Attach drive to system.
2. Verify drive atatched with "fdisk -l /dev/sda"
3. Create file system "mkfs.ext3 -j -T largefile /dev/sda2"

Actual results:

[root@penguin greg]# mkfs.ext3 -j -m 0 -T largefile /dev/sda2
mke2fs 1.34 (25-Jul-2003)
Floating point exception

Expected results:

File system should be created without error.

Additional info:

System is a AMD Athlon XP 2500+ system, motherboard is ASUS A7V8X-X,
enclosure is an ADS USB 2.0/1394 device but only using USB 2.0 at this
time.  I've tried both built-in USB ports as well as with an extra
card.  Same results using both USB ports so it's unlikely to be a USB
problem.  In addition the file system works fine (for the most part)
if the -T largefile option is not used.
Comment 1 Florian La Roche 2004-01-09 07:12:17 UTC 
Can you please check if the current rpm from the development tree
is also causing the same problem:
http://download.fedora.redhat.com/*    fedora/development/SRPMS/e2fspro*

Thanks a lot for your report,

Florian La Roche
Comment 2 Florian La Roche 2004-01-12 13:01:42 UTC 
As confirmed in private email, the newest rpm is fixing this problem.

Florian La Roche