Bug 69748

Summary: Unhandled Exception -- fsset.py, in badblocksDevice
Product: [Retired] Red Hat Linux Reporter: facility
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-07-24 22:33:07 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:
Attachments:
Description Flags
Crash dump from Anaconda none

Description facility 2002-07-24 22:32:06 UTC
When formatting with bad block check, installer crashes with debug info near the
very end of the format of the last partition.  First 2 non-swap partitions
format fine.


Version-Release number of selected component (if applicable):
Redhat 7.3 Anaconda.  Whatever was on the CDROM.  I don't know
where the version number is listed.

How Reproducible: Every time

1.Buy Wal-Mart computer. :)
2.Partitiion into 32M/512M/4G/25G
3.Format all partitions (ext3) checking for bad blocks

Actual Results:

Installer crashes with debug info near the very end of the format of the last
partition.  First 2 non-swap partitions format fine.
End of traceback looks like this.

  File "/usr/lib/anaconda/fsset.py", line 210, in badblocksDevice
    l = string.split(num, '/')
TypeError: argument 1: expected read-only character buffer, int found


Expected Results:

All partitions format with bad block check; and installer continues.


NOTE: attachment of Full crash dump will follow.

Additional Information:

Comment 1 facility 2002-07-24 22:33:02 UTC
Created attachment 66904 [details]
Crash dump from Anaconda

Comment 2 Michael Fulbright 2002-08-02 18:52:12 UTC
Bad blocks were detected and the installer crashed handling the exception.
You'll have to consider if you want to use the drive considering it failed the test.

*** This bug has been marked as a duplicate of 66181 ***