Hi Dave,
On Fri, 14 Jan 2011, Dave Miner wrote:
A couple of questions/comments on some specifics below.
On 01/13/11 03:32 PM, Alok Aggarwal wrote:
...
Target Validation
-----------------
Target Validation will be performed via the use of Shadow Lists
on the backend. The following is a list of all the validation
checks that will be made for the respective target entities
not counting the checks specific for GPT.
Partition
- Only one Solaris2 partition on a given disk should exist
- A maximum of 4 primary partitions can be present
- A maximum of 1 extended partition and at most 32 partitions
within that (one Solaris2 partition) can be present
- Partitions should not overlap
I presume you mean to say "must not"
Yes, it's a MUST not as opposed to SHOULD not (thankfully
this isn't an ietf list otherwise we'd spend days arguing
over such verbiage ;)).
- Partitions should not be too small for a given architecture
Can you clarify what "too small" means?
Restating:
- Partitions should be greater than a minimum size
That is, enforce the minimum size that 'zpool create' expects
(few hundred MB i think?).
Slice
- Number of slices must not exceed MAX_NSLICES
- Slice number must be MAX_NSLICES-1
- Slice size must be less than the size of a disk
- S2 must be the backup slice
- S1 must be swap slice (is this really even needed?)
The above two seem unnecessarily restrictive. They are conventions that we
ordinarily use, but a slice layout that doesn't conform to them would be
valid, I believe.
I know we need the S2 restriction atleast for VTOC otherwise
things go haywire. I recall that happening when during text
installer development, s2 was not being created due to a bug.
- Slices should not overlap
How about "Slices must overlap only with a full-disk backup slice"?
Yep. Of course even that overlap will not be allowed for GPT
disks.
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
