Bug 825310 - Requirements page mentions XFS, but not LVM as a requirement
Summary: Requirements page mentions XFS, but not LVM as a requirement
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Divya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 15:52 UTC by Jacob Shucart
Modified: 2016-09-20 05:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-10 07:15:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Jacob Shucart 2012-05-25 15:52:47 UTC
http://docs.redhat.com/docs/en-US/Red_Hat_Storage/2/html/User_Guide/index.html

If you go there, you will see that we mention XFS as a requirement.  It doesn't mention anything about the 512byte inode size which I thought was a requirement.  It also doesn't mention that users should be putting XFS on top of LVM.  As I understand, going forward certain features such as snapshots won't work unless users are configured on LVM, so we should probably add that here and include some information that makes sure they configure it properly so that snapshots will work going forward.

Comment 2 Divya 2012-06-21 12:49:25 UTC
I have added LVM as a requirement in Installation Guide and it is available at: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Installation_Guide/chap-Installation_Guide-Test_Chapter.html#sect-Installation_Guide-gssa_prepare-prerequisites_1

inode - I have added a new section called "Formatting Bricks", included increasing inode size information and it is available at: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html-single/Administration_Guide/index.html#id2659236

Comment 3 Anush Shetty 2012-07-06 09:34:58 UTC
Verified in the links above.


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