Description of problem:
The data partition on tui is default to "-1", user can set data partition form 0 to -1(all the left space), it will cause other issue when set data partition less then 256M, e.g. kdump fail or update fail.
So it is important to provide limit for minimum data partition size to 256MB.
It also fit for provide limit for minimum logging partition size to 2048MB.
http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-RHEV_Hypervisor_Kernel_Parameters_and_Automated_Installation-Storage_parameters.html#storage_vol_parameters
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121015.1.el6
How reproducible:
100%
Steps to Reproduce:
1. Go to partition size window during install
2. Focus on data partitiob.
3.
Actual results:
1. User can set data partition form 0 to -1(all the left space)
Expected results:
1. provide limit for minimum data partition size to 256MB.
2. Provide limit for minimum logging partition size to 2048MB.
Additional info:
Closing WONTFIX
1. provide limit for minimum data partition size to 256MB.
If users are upgrading via PXE or media instead of RHEV-M, then they're not using /data.
If kdump is remote (or not used), then we should be fine here too.
If set to 0, then we setup data an in memory filesystem like / is. As long as memory exists, we should be fine. It's an option we give to people, even if we recommend something different.
2. Provide limit for minimum logging partition size to 2048MB.
This was discussed back in the early days of RHEV-H. It was determined that we should default to a 2048 partition for logging, but not require it. It should require 5MB (fixed in a separate bug)