No, because the type of the disk is not necessary defined
(actually it is not unless you have a very similar disk),
and I don't think auto-configure will work because it requires
SCSI support which is not available for a vdisk built on top
of a volume.

alex.

Ian Matchett wrote:
> Would
> 
> format
> disk
> type
> 
> work as well?
> 
> IanM
> 
> Octave Orgeron wrote:
>> Hi Alex,
>>
>> Thanks! That worked perfectly! I had tried using dd, but forgot to use the 
>> "count=1". Now I see the correct label size. Thanks again! 
>>
>> Octave
>>
>>  *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>> Octave J. Orgeron
>> Solaris Systems Engineer
>> http://www.opensolaris.org/os/community/sysadmin/
>> http://unixconsole.blogspot.com
>> unixconsole at yahoo.com
>> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>>
>>
>>
>> ----- Original Message ----
>> From: Alexandre Chartre <Alexandre.Chartre at Sun.COM>
>> To: Octave Orgeron <unixconsole at yahoo.com>
>> Cc: ldoms-discuss at opensolaris.org
>> Sent: Monday, July 21, 2008 3:57:30 PM
>> Subject: Re: [ldoms-discuss] LDM 1.0.3 and Solaris 10 Update 4
>>
>>
>>   You are (or SVM is) probably reusing old data stored at the beginning of
>> the volume, and here this happens to be a valid disk label for a 100MB disk.
>> So try to remove that disk label:
>>
>>   # dd if=/dev/zero of=/dev/rdsk/c0d2s2 count=1
>>
>>   Or same command from the control domain with of=your SVM volume
>>
>> alex.
>>
>>
>> Octave Orgeron wrote:
>>   
>>> I have a system running with update 4 and the 127127-11 KU patch. I've 
>>> created both SVM and ZFS volumes and turned them into vdsdevs with no 
>>> options. So they should be presented as whole disks. However, this is what 
>>> I'm seeing in the guest domain:
>>>
>>> # format
>>> Searching for disks...done
>>>
>>>
>>> AVAILABLE DISK SELECTIONS:
>>>        0. c0d0 <DGC-RAID5-0219 cyl 32766 alt 2 hd 64 sec 10>
>>>           /virtual-devices at 100/channel-devices at 200/disk at 0
>>>        1. c0d1 <DGC-RAID5-0219 cyl 32766 alt 2 hd 64 sec 10>
>>>           /virtual-devices at 100/channel-devices at 200/disk at 1
>>>        2. c0d2 <SUN-DiskImage-100MB cyl 339 alt 2 hd 1 sec 600>
>>>           /virtual-devices at 100/channel-devices at 200/disk at 2
>>>        3. c0d3 <SUN-DiskImage-20GB cyl 4367 alt 2 hd 1 sec 9600>
>>>           /virtual-devices at 100/channel-devices at 200/disk at 3
>>> Specify disk (enter its number): ^D
>>>
>>> The c0d2 is a 6GB SVM soft partition, so the label is totally wrong. I've 
>>> tried this with different sized SVM volumes, no go. However, c0d3, which is 
>>> a ZFS 20G volume has the correct label. Is there an issue with SVM volumes 
>>> and VDS? I also noticed that if I don't use a SVM soft parition, it doesn't 
>>> work at all.. I end up seeing one of the underline disks in the meta 
>>> device, not the volume. Any ideas? Are there any recommended patches other 
>>> than the 127127-11 for u4?
>>>
>>> Thanks again!
>>>
>>> Octave
>>> --
>>> This message was posted from opensolaris.org
>>> _______________________________________________
>>> ldoms-discuss mailing list
>>> ldoms-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
>>>     
>>
>>
>>
>>       
>> _______________________________________________
>> ldoms-discuss mailing list
>> ldoms-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
>>   
> 
> -- 
> <http://www.sun.com/solaris>  * Ian Matchett *
> 
> *Sun Microsystems, Inc.*
> US
> Phone x22043/1 781 442 2043
> Mobile 413 237 6599
> Email Ian.Matchett at Sun.COM
> 

Reply via email to