Bug 113150 - mkfs.ext3 with -T largefile gets Floating point exception
Summary: mkfs.ext3 with -T largefile gets Floating point exception
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: e2fsprogs
Version: 1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-08 22:13 UTC by Gregory Gulik
Modified: 2007-11-30 22:10 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-01-12 13:01:42 UTC


Attachments (Terms of Use)

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



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