All of lore.kernel.org
 help / color / mirror / Atom feed
From: liushengchao02 at meituan.com
To: spdk@lists.01.org
Subject: [SPDK] On the resize of bdevs with iSCSI initiator backend or NVMf backend
Date: Wed, 18 Aug 2021 03:30:46 +0000	[thread overview]
Message-ID: <20210818033046.2778.41917@ml01.vlan13.01.org> (raw)

[-- 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.

                 reply	other threads:[~2021-08-18  3:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210818033046.2778.41917@ml01.vlan13.01.org \
    --to=spdk@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.