Przem,

> Anybody has an idea what I can do about it?

zfs set shareiscsi=off vol01/zvol01
zfs set shareiscsi=off vol01/zvol02

Doing this will have no impact on the LUs if configured under COMSTAR.
This will also transparently go away with b136, when ZFS ignores the shareiscsi 
property.

- Jim


> 
> On 04/05/2010 16:43, "eXeC001er" <execoo...@gmail.com> wrote:
> 
>> Perhaps the problem is that the old version of pool have shareiscsi, but new
>> version have not this option, and for share LUN via iscsi you need to make
>> lun-mapping.
>> 
>> 
>> 
>> 2010/5/4 Przemyslaw Ceglowski
>> <prze...@ceglowski.net<mailto:prze...@ceglowski.net>>
>> Jim,
>> 
>> On May 4, 2010, at 3:45 PM, Jim Dunham wrote:
>> 
>>>> 
>>>> On May 4, 2010, at 2:43 PM, Richard Elling wrote:
>>>> 
>>>>> On May 4, 2010, at 5:19 AM, Przemyslaw Ceglowski wrote:
>>>>> 
>>>>>> It does not look like it is:
>>>>>> 
>>>>>> r...@san01a:/export/home/admin# svcs -a | grep iscsi
>>>>>> online         May_01   svc:/network/iscsi/initiator:default
>>>>>> online         May_01   svc:/network/iscsi/target:default
>>>>> 
>>>>> This is COMSTAR.
>>>> 
>>>> Thanks Richard, I am aware of that.
>>> 
>>> Since you upgrade to b134, not b136 the iSCSI Target Daemon is still around,
>>> just not on our system.
>>> 
>>> IPS packaging changes have not installed the iSCSI Target Daemon (among 
>>> other
>>> things) by default. It is contained in IPS package known as either
>>>> SUNWiscsitgt or network/iscsi/target/legacy. Visit your local package
>>> repository for updates: http://pkg.opensolaris.org/dev/
>>> 
>>> Of course starting with build 136..., iSCSI Target Daemon (and ZFS
>>> shareiscsi) are gone, so you will need to reconfigure your two ZVOLs
>>> 'vol01/zvol01' >and 'vol01/zvol02', under COMSTAR soon.
>>> 
>>> http://wikis.sun.com/display/OpenSolarisInfo/How+to+Configure+iSCSI+Target+Po
>>> rts
>>> http://wikis.sun.com/display/OpenSolarisInfo/COMSTAR+Administration
>>> 
>>> - Jim
>> 
>> The migrated zVols have been running under COMSTAR originally on b104 which
>> makes me wonder even more. Is there any way I can get rid of those messages?
>> 
>>> 
>>>> 
>>>>> 
>>>>>> _
>>>>>> Przem
>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> ________________________________________
>>>>>>> From: Rick McNeal [ramcn...@gmail.com<mailto:ramcn...@gmail.com>]
>>>>>>> Sent: 04 May 2010 13:14
>>>>>>> To: Przemyslaw Ceglowski
>>>>>>> Subject: Re: [storage-discuss] iscsitgtd failed request to share on
>>>>>>> zpool import after upgrade from b104 to b134
>>>>>>>> 
>>>>>>> Look and see if the target daemon service is still enabled. COMSTAR
>>>> has been the official scsi target project for a while now. In fact, the
>>>> old iscscitgtd >was removed in build 136.
>>>>> 
>>>>> For Nexenta, the old iscsi target was removed in 3.0 (based on b134).
>>>>> -- richard
>>>> 
>>>> It does not answer my original question.
>>>> -- Przem
>>>> 
>>>>> 
>>>>>>> 
>>>>>>> Rick McNeal
>>>>>>> 
>>>>>>> 
>>>>>>> On May 4, 2010, at 5:38 AM, Przemyslaw Ceglowski
>>>>>>> <prze...@ceglowski.net<mailto:prze...@ceglowski.net>> wrote:
>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> I am posting my question to both storage-discuss and zfs-discuss
>>>>>>>> as I am not quite sure what is causing the messages I am receiving.
>>>>>>>> 
>>>>>>>> I have recently migrated my zfs volume from b104 to b134 and
>>>>>>>> upgraded it from zfs version 14 to 22. It consist of two zvol's
>>>>>>>> 'vol01/zvol01' and 'vol01/zvol02'.
>>>>>>>> During zpool import I am getting a non-zero exit code, however the
>>>>>>>> volume is imported successfuly. Could you please help me to understand
>>>>>>>> what could be the reason of those messages?
>>>>>>>> 
>>>>>>>> r...@san01a:/export/home/admin#zpool import vol01
>>>>>>>> r...@san01a:/export/home/admin#cannot share 'vol01/zvol01':
>>>>>>>> iscsitgtd failed request to share
>>>>>>>> r...@san01a:/export/home/admin#cannot share 'vol01/zvol02':
>>>>>>>> iscsitgtd failed request to share
>>>>>>>> 
>>>>>>>> Many thanks,
>>>>>>>> Przem
>>>>>>>> _______________________________________________
>>>>>>>> storage-discuss mailing list
>>>>>>>> storage-disc...@opensolaris.org<mailto:storage-disc...@opensolaris.org>
>>>>>>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>>>>>> _______________________________________________
>>>>>> zfs-discuss mailing list
>>>>>> zfs-discuss@opensolaris.org<mailto:zfs-discuss@opensolaris.org>
>>>>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>>>> 
>>>>> --
>>>>> ZFS storage and performance consulting at http://www.RichardElling.com
>>>> _______________________________________________
>>>> storage-discuss mailing list
>>>> storage-disc...@opensolaris.org<mailto:storage-disc...@opensolaris.org>
>>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss@opensolaris.org<mailto:zfs-discuss@opensolaris.org>
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>> 
> 


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to