This is a discussion on New disks / logical drive on StorEdge 3310 uses slice 6 instead of slice 0 ?? within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Hi, My existing Host LUN map partitions, when viewed from the format command, always have slice 0: Current partition ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, My existing Host LUN map partitions, when viewed from the format command, always have slice 0: Current partition table (original): Total disk cylinders available: 25096 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 usr wm 2 - 25095 97.64GB (25094/0/0) 204767040 1 unassigned wm 0 0 (0/0/0) 0 2 unassigned wm 0 0 (0/0/0) 0 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 usr wu 0 - 1 7.97MB (2/0/0) 16320 Now a new partition mapped to LUN 5, after having changed its type to "Auto configure (0)" in the format menu, uses slice 6 ... and slice 0 and 1 have 131 each reserved for some purpose: Current partition table (original): Total disk cylinders available: 45049 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 32 131.48MB (33/0/0) 269280 1 swap wu 33 - 65 131.48MB (33/0/0) 269280 2 backup wu 0 - 45048 175.29GB (45049/0/0) 367599840 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 66 - 45048 175.03GB (44983/0/0) 367061280 7 unassigned wm 0 0 (0/0/0) 0 Is this a new behaviour with disks on 3310 ? What changed this behaviour ?? |