All of lore.kernel.org
 help / color / mirror / Atom feed
* [SPDK] On the resize of bdevs with iSCSI initiator backend or NVMf backend
@ 2021-08-18  3:30 liushengchao02
  0 siblings, 0 replies; only message in thread
From: liushengchao02 @ 2021-08-18  3:30 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

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 users can use the connected remote storage without interruption (with the help 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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-08-18  3:30 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-18  3:30 [SPDK] On the resize of bdevs with iSCSI initiator backend or NVMf backend liushengchao02

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.