Bug 124956 - mksf.ext3 -T largefile -> floating point error
Summary: mksf.ext3 -T largefile -> floating point error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: e2fsprogs
Version: 1
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-01 16:16 UTC by l ciani
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-02 17:18:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description l ciani 2004-06-01 16:16:35 UTC
Description of problem: 
I have deleted all windows partition from my second hard-drive 
(/dev/hdb) using fdisk. None of the partitions of that disk were 
mounted, obviously. 
I have then created one single linux partition on that disk, again 
with fdisk. 
Finally I invoked /sbin/mkfs.ext3 -T largefile /dev/hdb1 
I have used the -T switch because I am going to use this drive to 
edit large video files. 
I was greeted by the following message: 
[root@mysystem]# /sbin/mkfs.ext3 -T largefile /dev/hdb1 
mke2fs 1.34 (25-Jul-2003) 
Errore di virgola mobile 
(that's Italian for "Floating point error") 
 
 
 
Version-Release number of selected component (if applicable): 
util-linux-2.11y-29 
 
 
How reproducible: 
For instance, run "mkfs.ext3 -T largefile /dev/newly-formatted-drive" 
 
Steps to Reproduce: 
1. format a hard-disk on /dev/hdb (mine is a 20GB Quantum Fireball 
Lct10) 
2. create a single linux partition 
3. run mkfs.ext3 -T largefile /dev/hdb1 
   
Actual results: 
[root@mysystem]# /sbin/mkfs.ext3 -T largefile /dev/hdb1 
mke2fs 1.34 (25-Jul-2003) 
Errore di virgola mobile 
 
 
Expected results: 
No error messages 
 
Additional info: 
I succesfully formated the drive omitting the -T largefile parameter.

Comment 1 Elliot Lee 2004-06-02 17:18:09 UTC
Please try FC2. I can't reproduce the bug with the e2fsprogs included
in it.


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