.LUN resize on target side Ceph is now reflected on clients
Previously, when using the iSCSI gateway, resized Logical Unit Numbers (LUNs) were not immediately visible to initiators. This required a work around of restarting the iSCSI gateway after resizing a LUN to expose it to the initiators.
With this update to {product}, iSCSI initiators can now see a resized LUN immediately after rescan.
Description of problem:
LUN resize done through gwcli is not getting reflected on client leading to issues.
[Tejas]
In my functional testing had a few observations.
>>>> >> >
>>>> >> > 1. Lun resize( disk resize ) on the ceph target does not reflect on any
>>>> >> > of
>>>> >> > the clients(RHEL,ESX,Win), even after re-scanning the storage.
[Jason]:
I looked at the config on banshee where rbd/test1 was a 40GB image but
> buckeye was seeing it as 10GB.
>
> The configfs on banshee appears to be correct:
>
> # cat /sys/kernel/config/target/core/user_3/rbd.test1/info
> Status: ACTIVATED Max Queue Depth: 0 SectorSize: 512 HwMaxSectors: 128
> Config: rbd/rbd/test1/osd_op_timeout=30 Size: 42949672960
>
> The device size on buckeye is incorrect:
>
> # blockdev --getsize64 /dev/sdh
> 10737418240
[Mike]:
This is a tcmu-runner and kernel issue. It's on my TODO. I have a simple
userspace patch for downstream only to work around some RHEL kernel issues.
@Mike: look like this just needs the change in ceph-iscsi-config to alert target of the size change? I used gwcli to resize the image and restarted rbd-target-gw and the initiator was able to detect the change.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:2819
Description of problem: LUN resize done through gwcli is not getting reflected on client leading to issues. [Tejas] In my functional testing had a few observations. >>>> >> > >>>> >> > 1. Lun resize( disk resize ) on the ceph target does not reflect on any >>>> >> > of >>>> >> > the clients(RHEL,ESX,Win), even after re-scanning the storage. [Jason]: I looked at the config on banshee where rbd/test1 was a 40GB image but > buckeye was seeing it as 10GB. > > The configfs on banshee appears to be correct: > > # cat /sys/kernel/config/target/core/user_3/rbd.test1/info > Status: ACTIVATED Max Queue Depth: 0 SectorSize: 512 HwMaxSectors: 128 > Config: rbd/rbd/test1/osd_op_timeout=30 Size: 42949672960 > > The device size on buckeye is incorrect: > > # blockdev --getsize64 /dev/sdh > 10737418240 [Mike]: This is a tcmu-runner and kernel issue. It's on my TODO. I have a simple userspace patch for downstream only to work around some RHEL kernel issues.