On 03/31/10 11:25 AM, Alexander Eremin wrote:
# tdmgtst -d -vvv
...
Discovering disk 2) # EFI labeled
      disk 2)
            ddm_disk_size=143374738 (uint64)
            ddm_disk_block_size=512 (uint32)
            ddm_disk_mtype=1 (uint32)
            ddm_disk_name=c0t0d0
            ddm_disk_dev_id=id1,s...@n500000e0136e8da0
            ddm_disk_devicepath=/p...@780/p...@0/p...@9/s...@0/s...@0,0
            ddm_disk_vendor_id=FUJITSU
            ddm_disk_product_id=MAY2073RCSUN72G
            ddm_disk_opath=/dev/rdsk/c0t0d0s0
            ddm_disk_ctype=scsi
            ddm_disk_label=2 (uint32)
     Discovering disk 3)
      disk 3)
            ddm_disk_size=143374738 (uint64)
            ddm_disk_block_size=512 (uint32)
            ddm_disk_mtype=1 (uint32)
            ddm_disk_nheads=24 (uint32)
            ddm_disk_nsectors=424 (uint32)
            ddm_disk_name=c0t1d0
            ddm_disk_dev_id=id1,s...@n500000e0136e8e30
            ddm_disk_devicepath=/p...@780/p...@0/p...@9/s...@0/s...@1,0
            ddm_disk_vendor_id=FUJITSU
            ddm_disk_product_id=MAY2073RCSUN72G
            ddm_disk_opath=/dev/rdsk/c0t1d0s0
            ddm_disk_ctype=scsi
            ddm_disk_label=1 (uint32)

No info about nheads  available for EFI-labeled disk.

As Sean pointed out, for x86 that might be caused by 6937739.
Installer currently relies on nheads, nsectors available for
x86 disk.

Need a fix for sparc too.

I have looked at the orchestrator and it does not utilized cylinder
information in case of Sparc.
If user customizes VTOC via AI manifest, adjustments to cylinders
are not done in orchestrator, instead VTOC information
is passed to Target Instantiation which makes sure that
slices to be created start and end on cylinder boundary [1]
(TI calls DKIOCGGEOM to obtain cylinder size) [2].

Based on this, orchestrator (target_discovery.c) should tolerate
if nheads, nsectors information is not available for Sparc.
Once the installation started, orchestrator could call Target
Instantiation to label the disk (if needed) and then subsequent
call to TI to create VTOC would succeed, since DKIOCGGEOM
would provide [2] with needed information about cylinder size,
since disk would be already labeled.

Jan


References:
[1] http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/lib/libti/ti_dm.c#idm_adjust_vtoc [2] http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/lib/libti/ti_dm.c#idm_create_vtoc

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to