On 03/30/10 03:46 AM, Alexander Eremin wrote: > Hi all, > reflecting on the possible fix for 6260 (sparc AI need a way to > mechanism to explicitly ask for creating label on Sparc disk), I > encountered a problem - a liborchestrator in the Target Discovery > process ignores non-labeled disk and disk_criteria_match function do > not test this disk. > ... > <AI Mar 30 06:23:46> Initiating Target Discovery... > <OM Mar 30 06:23:49> Ignoring c0t0d0 because of bad Geometry > <AI Mar 30 06:23:53> Target Discovery finished successfully > <AI Mar 30 06:23:53> testing disk c0t2d0 > <AI Mar 30 06:23:53> testing disk c0t3d0 > <AI Mar 30 06:23:53> testing disk c0t1d0 > <AI Mar 30 06:23:53> Searching for a disk target matching the following > criteria > <AI Mar 30 06:23:53> Disk name: c0t0d0 > <AI Mar 30 06:23:53> Disk c0t2d0 doesn't match desired name c0t0d0 > <AI Mar 30 06:23:53> Disk c0t3d0 doesn't match desired name c0t0d0 > <AI Mar 30 06:23:53> Disk c0t1d0 doesn't match desired name c0t0d0 > <AI Mar 30 06:23:53> No disk that matches all manifest criteria was > found > <AI Mar 30 06:23:53> Could not find a disk based on manifest criteria > <AI Mar 30 06:23:53> ai target device not found > ... > As you see, c0t0d0 was removed from target searching. > In this case, perhaps labeling the disk on early stage is needed, before > Target Discovery. > I'd like to know your opinion. >
I don't believe that labeling disks automatically during discovery is a good idea, as there is no expectation that anything will be written to a disk prior to initiating an installation. Seems like we should think about how to get TD to not ignore the disk and make the apps capable of dealing with the lack of geometry. Dave
