Bug 610109 - Can XFS be shrunk, or just grown?
Summary: Can XFS be shrunk, or just grown?
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: Red_Hat_Enterprise_Linux-Release_Notes-6-en-US
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Ryan Lerch
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-01 15:12 UTC by Chris Pepper
Modified: 2010-11-11 15:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 15:24:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Pepper 2010-07-01 15:12:19 UTC
Description of problem:
If XFS can be grown but shrunk, then don't say 'resized'.

The XFS file systems can also be defragmented and resized (i.e. enlarged) while mounted and active.

Version-Release number of selected component (if applicable):
6b2

How reproducible:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Beta_2_Release_Notes/filesystems.html

Actual results:
Copy says "resized (i.e. enlarged)"
 
Expected results:
Copy should say "expanded" or something clearer.

Comment 2 RHEL Program Management 2010-07-01 15:43:23 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Ryan Lerch 2010-07-09 03:33:12 UTC
Reworded to:

XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file systems can also be defragmented and expanded while mounted and active.

cheers,
ryanlerch

Comment 8 releng-rhel@redhat.com 2010-11-11 15:24:36 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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