Bug 801159 - Writing partition schem could be really slow, no feedback to the user
Summary: Writing partition schem could be really slow, no feedback to the user
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 19:36 UTC by Kevin Raymond
Modified: 2012-03-08 17:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-08 14:47:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kevin Raymond 2012-03-07 19:36:27 UTC
While formating, and setting a LVM on big (1 Tera) hard drive disk, writing partition table, setting blocks, writing inode tables etc. could be *really* long. It tooks me more than 4hours!!! 

And the user has just the blue bar going from left to right and backward, without knowing what is happening. Only a fuzzy message is printed, like writing /dev/sda1 partition (for 3hours?!)

From the text console, I got things moving with several steps like
writing partition table: 1/5557
…
…
Writing inodes table: 1/5557
…
…

Showing the blocks ration will tell the user that the process is still going forward…

I were using F17 Alpha and ext4 format.

Comment 1 Chris Lumens 2012-03-08 14:47:01 UTC
Screen scraping to display progress is almost always a bad idea, because it ties us to today's particular output format and means our progress reporting is going to break whenever the other program changes.  Sorry it took so long for you.  This is likely related to other disk slowness we've been hearing about.  I formatted a very large drive a few weeks back and it did not take anything near three hours.

Comment 2 Kevin Raymond 2012-03-08 17:39:54 UTC
Ok, understood.
On the new design, I hope the user will know at least that things are moving :)


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