I noticed this

[vob.iscsi.discovery.login.error] discovery failure on vmhba64 to
10.10.35.202 because the target returned a login status of 0201.

A restart of rbd services will require reentering chap credentials on
targets ?

Steven

On Fri, 25 Oct 2019 at 09:57, Steven Vacaroaia <ste...@gmail.com> wrote:

> Yes, I did.
> I event restarted rbd-target services
>
> uname -a
> Linux osd01.chi.medavail.net 4.18.11-1.el7.elrepo.x86_64 #1 SMP Sat Sep
> 29 09:42:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
> [root@osd01 ~]# rpm -qa | grep tcmu
> tcmu-runner-1.4.0-1.el7.x86_64
>
> On Fri, 25 Oct 2019 at 09:51, Jason Dillaman <jdill...@redhat.com> wrote:
>
>> On Fri, Oct 25, 2019 at 9:49 AM Steven Vacaroaia <ste...@gmail.com>
>> wrote:
>> >
>> > Thanks for your prompt response
>> > Unfortunately , still no luck
>> > Device shows with correct size under "Device backing" but not showing
>> at all  under "increase datastore capacity)
>> >
>> > resize rbd.rep01 7T
>> > ok
>> > /disks> ls
>> > o- disks
>> .........................................................................................................
>> [13.0T, Disks: 2]
>> >   o- rbd.rep01
>> ........................................................................................................
>> [rep01 (7T)]
>>
>> Did you rescan the LUNs in VMware after this latest resize attempt?
>> What kernel and tcmu-runner version are you using?
>>
>> > On Fri, 25 Oct 2019 at 09:24, Jason Dillaman <jdill...@redhat.com>
>> wrote:
>> >>
>> >> On Fri, Oct 25, 2019 at 9:13 AM Steven Vacaroaia <ste...@gmail.com>
>> wrote:
>> >> >
>> >> > Hi,
>> >> > I am trying to increase size of a datastore made available through
>> ceph iscsi rbd
>> >> > The steps I followed are depicted below
>> >> > Basically gwcli report correct data and even VMware device capacity
>> is correct but when tried to increase it there is no device listed
>> >> >
>> >> > I am using ceph-iscsi-config-2.6-42.gccca57d.el7 and ceph 13.2.2
>> >> >
>> >> > Any guidance/help will be appreciated
>> >> >
>> >> > 1. increase rbd size
>> >> > rbd -p rbd resize --size 6T rep01
>> >> > Resizing image: 100% complete...done.
>> >>
>> >> Never resize the RBD images backing a LUN via the "rbd" CLI -- use
>> >> "gwcli" to resize the images and it will handle resizing the LUNs.
>> >>
>> >> > 2. restart gwcli
>> >> >  systemctl restart rbd-target-gw &&  systemctl restart rbd-target-api
>> >> >
>> >> > 3 check size
>> >> >  gwcli
>> >> > /iscsi-target...go-ceph/hosts> ls
>> >> > o- hosts
>> ....................................................................................................
>> [Hosts: 8: Auth: CHAP]
>> >> >   o- iqn.1998-01.com.vmware:vsan5-66c18541
>> ................................................ [LOGGED-IN, Auth: CHAP,
>> Disks: 2(12.0T)]
>> >> >   | o- lun 0
>> ....................................................................................
>> [rbd.vmware01(6.0T), Owner: osd01]
>> >> >   | o- lun 1
>> .......................................................................................
>> [rbd.rep01(6.0T), Owner: osd02]
>> >> >
>> >> > 4. VMware rescan devices
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ceph-users mailing list
>> >> > ceph-users@lists.ceph.com
>> >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>> >>
>> >>
>> >>
>> >> --
>> >> Jason
>> >>
>>
>>
>> --
>> Jason
>>
>>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to