Bug 673464 - Unable to resize logical partitions using 'parted'
Summary: Unable to resize logical partitions using 'parted'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: parted
Version: 5.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-28 10:17 UTC by Savitha
Modified: 2011-07-28 16:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-28 16:45:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Savitha 2011-01-28 10:17:26 UTC
Description of problem:
Resizing the logical partitions using parted returns "Error: File system has an incompatible feature enabled." error.

Version-Release number of selected component (if applicable):
Redhat 5.6

Steps to Reproduce:
1. Create partitions on host storage device - 1 extended and 1 logical (maximum size).
2. Create ext3 fs, mount and copy data 
3. Expand back-end LUN (created metaLUN) 
4. Unmount filesystem 
5. blockdev --rereadpt <device>
6. Verify larger size is seen in output of /proc/partitions 
7. Use parted 'resize' command to resize partitions
  a. resize of extended partition is successful - no error message
  b. resize of logical partition fails with message "Error: File system has an incompatible feature enabled."
  
Expected results:
Resize should complete successfully.

Comment 1 David Cantrell 2011-07-27 18:23:10 UTC
Do not use parted to resize filesystems.  Use the native filesystem tools to do that, then adjust the partition table using parted (or fdisk).

Comment 2 Savitha 2011-07-28 05:04:03 UTC
By 'native filesystem tools', are you referring to e2fsck and resize2fs utility? 

-Savitha

Comment 3 Brian Lane 2011-07-28 16:45:53 UTC
Yes, assuming that is the filesystem you are using.


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