From: Benjamin Coddington <bcodding@redhat.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/3] pNFS blocklayout handling for transient devices
Date: Fri, 8 Dec 2017 12:52:56 -0500 [thread overview]
Message-ID: <cover.1512748321.git.bcodding@redhat.com> (raw)
This set improves the blocklayoutdriver's handling of layouts when devices
are not present on the a client, or become unavailable. Ideally, clients
should not continually spam a server with LAYOUTGET for known layouts, and
GETDEVINFO for known devices, since it may be a common scenario to have some
clients that have access to the block devices, and some clients that do not.
In addition to better handling situations where devices are unavailable,
patches 2 and 3 fix crashes if SCSI devices do not exist or are already have
existing reservations.
Benjamin Coddington (3):
pnfs/blocklayout: set PNFS_LAYOUTRETURN_ON_ERROR
pnfs/blocklayout: Revalidate SCSI disks after registration
pnfs/blocklayout: handle transient devices
fs/nfs/blocklayout/blocklayout.c | 84 +++++++++++++++++++++++++++++++++++++---
fs/nfs/blocklayout/dev.c | 15 ++++---
fs/nfs/pnfs.c | 2 +-
fs/nfs/pnfs.h | 6 ++-
fs/nfs/pnfs_dev.c | 1 -
5 files changed, 94 insertions(+), 14 deletions(-)
--
2.9.3
next reply other threads:[~2017-12-08 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 17:52 Benjamin Coddington [this message]
2017-12-08 17:52 ` [PATCH v1 1/3] pnfs/blocklayout: set PNFS_LAYOUTRETURN_ON_ERROR Benjamin Coddington
2017-12-08 17:52 ` [PATCH v1 2/3] pnfs/blocklayout: Revalidate SCSI disks after registration Benjamin Coddington
2017-12-12 14:38 ` Christoph Hellwig
2017-12-13 2:23 ` Benjamin Coddington
2017-12-13 15:53 ` Benjamin Coddington
2017-12-08 17:52 ` [PATCH v1 3/3] pnfs/blocklayout: handle transient devices Benjamin Coddington
2017-12-12 14:29 ` [PATCH v1 0/3] pNFS blocklayout handling for " Christoph Hellwig
2017-12-13 2:37 ` Benjamin Coddington
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=cover.1512748321.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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