On Sun, 20 Jul 2008, ak wrote:

> I dont understand clearly what is disk slice partition. How to do this?

Partitioning can be a very confusing concept, agreed.

It's best to think of it as a hierarchical (tree-structured) way of 
subdividing the space on a physical disk. Like this:

DISK
   |
   +--->        partition 1
   |
   +--->        partition 2
   .
   .
   .
   +---> partition N

This is a depth-one partitioning scheme.
You can "extend" that to:

DISK
   |
   +--->        partition 1 ("extended")
   |        |
   |        +-> extended (sub-)partition (N+1)
   |        +-> extended (sub-)partition (N+2)
   |        .
   |        +-> extended (sub-)partition (N+M)
   |
   +--->        partition 2
   .
   .
   .
   +---> partition N

You can also "slice" it to:

DISK
   |
   +--->        partition 1 ("container" VTOC)
   |        |
   |        +-> slice (1)
   |        +-> slice (2)
   |        .
   |        +-> slice (M)
   |
   +--->        partition 2
   .
   .
   .
   +---> partition N

You can have combinations of the two of the sort:

DISK
   |
   +--->        partition 1 ("extended")
   |        |
   |        +-> extended (sub-)partition (N+1)
   |        +-> extended (sub-)partition (N+2)
   |        .
   |        +-> extended (sub-)partition (N+M)
   |
   +--->        partition 2 ("container" VTOC)
   |        |
   |        +-> slice (1)
   |        +-> slice (2)
   |        .
   |        +-> slice (K)
   .
   .
   .
   +---> partition N

And if you happen to use a logical volume manager like Solaris SVM or 
Linux LVM, you can even have something like:

DISK
   |
   +--->        partition 1 ("extended")
   |        |
   |        +-> extended (sub-)partition (N+1)
   |        |   (Linux LVM physical)
   |        |           |
   |        |           +-----> LVM logical 1
   |        |           .
   |        |           +-----> LVM logical x
   |        |
   |        +-> extended (sub-)partition (N+2)
   |        .
   |        +-> extended (sub-)partition (N+M)
   |
   +--->        partition 2 ("container" - VTOC)
   |        |
   |        +-> slice (1)
   |        |   (Solaris SVM subdisk)
   |        |           |
   |        |           +-----> SVM softpartition 1
   |        |           .
   |        |           +-----> SVM softpartition y
   |        |
   |        +-> slice (2)
   |        .
   |        +-> slice (K)
   .
   .
   .
   +---> partition N


The names of the subdividing units are different depending on the scheme 
used - and so are the exact data structures that are written to the disk 
to indicate the subdivisions. I.e. "extended partitions" use different 
data structures than "volumes" which use different data structures than 
"slices".

This causes a lot of naming confusion, agreed; in the end, it's an 
administrative detail. The above schematic diagrams hopefully make it a 
bit clearer ?


(As far as the question goes, "what is allowed/acceptable", that's more 
involved not sure I'll have enough time to write that up anywhen soon)

Best regards,
FrankH.

>
>
> This message posted from opensolaris.org
> _______________________________________________
> docs-discuss mailing list
> docs-discuss at opensolaris.org
>

------------------------------------------------------------------------------
No good can come from selling your freedom, not for all the gold in the world,
for the value of this heavenly gift far exceeds that of any fortune on earth.
------------------------------------------------------------------------------

Reply via email to