Bug 1399997 - formating ext4 fs become much more slower then in 6.7
Summary: formating ext4 fs become much more slower then in 6.7
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 08:55 UTC by Levente Farkas
Modified: 2017-12-06 12:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:35:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Levente Farkas 2016-11-30 08:55:46 UTC
in the previous version 6.7 the disk formating was much faster then in the current 6.8 version. the time changed from 17 sec to 15 minutes (not second)!!! it seems the differences in these 2 directories :
6.8/os/x86_64/images
6.8/os/x86_64/isolinux
if i overwrite these directories for 6.7 (eg into a pxe install directory) then everything still working but much faster as i wrote the time above.


Just add a few big disk and select it as one big (ie full disk) partition and select to format them to ext4.

Comment 4 Jan Kurik 2017-12-06 12:35:00 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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