On Mon, 17 Jan 2011, Darren Kenny wrote:
On 14/01/2011 23:00, Alok Aggarwal wrote:
- 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?).
Is this not the OS minimum size, not the minimum size for a zpool?
I was proposing the latter check but you bring up a good
point that perhaps it should be the former.
If it is the OS minimum size, where does that information come from?
I know with a CD, the estimated size is stored in a 'dot-file' but how would one
determine this minimum size for an AI type install where it's all dependent on
the packages to be installed.
I believe that the size is hardcoded at present in AI (unless
that has changed in the last few months).
It would seem to be something that the 'Transfer' module could provide, but I
think it would be quite time-consuming to actually determine a real value.
What would be an acceptable 'estimate'?
An orthogonal question here is - if Target is to be responsible
for ensuring that a disk/slice is atleast the minimum OS size,
then there needs to be an API to communicate the minimum OS size
to Target.
The app/MVC would determine the minimum OS size (by looking at
the dot file or by calling transfer) and subsequently call an API
to let Target know that value.
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
