On Jan 3, 2013, at 3:33 PM, Eugen Leitl wrote:
> On Thu, Jan 03, 2013 at 03:21:33PM -0600, Phillip Wagstrom wrote:
>> Eugen,
>>
>> Be aware that p0 corresponds to the entire disk, regardless of how it
>> is partitioned with fdisk. The fdisk partitions are 1 - 4. By using p0 for
>> log and p1 for cache, you could very well be writing to same location on the
>> SSD and corrupting things.
>
> My partitions are like this:
>
> partition> print
> Current partition table (original):
> Total disk cylinders available: 496 + 2 (reserved cylinders)
>
> Part Tag Flag Cylinders Size Blocks
> 0 unassigned wm 0 0 (0/0/0) 0
> 1 unassigned wm 0 0 (0/0/0) 0
> 2 backup wu 0 - 11709 70.04GB (11710/0/0) 146890240
> 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 unassigned wm 0 0 (0/0/0) 0
> 8 boot wu 0 - 0 6.12MB (1/0/0) 12544
> 9 unassigned wm 0 0 (0/0/0) 0
>
> am I writing to the same location?
Okay. The above are the slices within the Solaris fdisk partition.
These would be the "s0" part of "c0t0d0s0". These are modified with via format
under "partition".
p1 through p4 refers to the x86 fdisk partition which is administered
with the fdisk command or called from the format command via "fdisk"
>
>> Personally, I'd recommend putting a standard Solaris fdisk partition on
>> the drive and creating the two slices under that.
>
> Which command invocations would you use to do that, under Open Indiana?
format -> partition then set the size of each there.
-Phil
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
