Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: jasonm at ami.com
To: spdk@lists.01.org
Subject: [SPDK] Lvol sync issues running SPDK on separate hosts connected via dual port drives
Date: Fri, 20 Dec 2019 20:07:45 +0000	[thread overview]
Message-ID: <20191220200745.2770.77019@ml01.vlan13.01.org> (raw)

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

I'm trying to see logical volumes created by SPDK_A on SPDK_B, but the only way I can see them is if I reboot the NODE_B system running SPDK_B.  What needs to be done in order to sync the logical volumes on a namespace between two SPDKs running on separate hosts (namespace sharing)?  Is this even possible?

My system setup is described below.  I have confirmed namespace sharing works with the Linux kernel driver (not LVS just namespace).  SPDK version is 19.04.00,  Kernel 4.15.0-29,  Distro Ubuntu 18.04.1 LTS.

DUAL PORT CHASSIS
- NODE_A
--- SPDK_A (create volume store, create volumes)

- NODE_B
--- SPDK_B (must be rebooted to see logical volumes created)

                 reply	other threads:[~2019-12-20 20:07 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=20191220200745.2770.77019@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox