From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============5113887977643869916=="
MIME-Version: 1.0
From: liushengchao02 at meituan.com
Subject: [SPDK] On the resize of bdevs with iSCSI initiator backend or NVMf
 backend
Date: Wed, 18 Aug 2021 03:30:46 +0000
Message-ID: <20210818033046.2778.41917@ml01.vlan13.01.org>
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============5113887977643869916==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hello,

We are studying SPDK and preparing for remote storage applications.

After testing, I find that bdevs created by bdev_iscsi_create or bdev_nvme_=
attach_controller can't resize accordingly when the connected remote target=
 block devices have been resized online.

However, when using 'nvme connect' or 'iscsiadmin' commands, the connected =
block devices can resize accordingly as remote storage resizes and local us=
ers can use the connected remote storage without interruption (with the hel=
p of resize2fs or xfs_growfs).

I learned that SPDK support resize of bdevs with ceph rbd or logical volume=
 beckend (i.e. bdevs created by bdev_rbd_create and bdev_lvol_create).

Dose SPDK support or will support the resize of iSCSI and NVMf backend when=
 the connected remote target has been resized?

Thank you very much.
--===============5113887977643869916==--