Bug 661520 - Maximum supported GFS File System size is incorrect. (RHEL 5.6)
Summary: Maximum supported GFS File System size is incorrect. (RHEL 5.6)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: doc-Global_File_System_Guide
Version: 5.6
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 660364 661518
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-08 21:56 UTC by Steven J. Levine
Modified: 2011-04-14 04:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 661518
Environment:
Last Closed: 2011-04-14 04:49:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Steve Whitehouse 2010-12-09 10:58:20 UTC
Why has this been cloned twice for rhel5? Is one bug different to the other for some reason?

Comment 2 Steven J. Levine 2010-12-10 19:52:18 UTC
One bz is for GFS, one for GFS2 -- both of which contained the same outdated information. Separate bugs for separate manuals.

This may not be strictly necessary, but it's a record-keeping thing.

Comment 3 RHEL Program Management 2010-12-14 05:17:33 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 Steve Whitehouse 2010-12-15 11:19:59 UTC
RE: comment #2

I see now! Sorry didn't spot that earlier.


Setting blocker otherwise this won't make 5.6

Comment 5 Steven J. Levine 2010-12-21 21:48:12 UTC
I have corrected the maximum file system size information in the RHEL 5.6 draft of the gfs manual and I have checked that draft into the svn repository. The corrected information should be available at the RHEL 5.6 release.


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