Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: linux-fsdevel@vger.kernel.org,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH 3/3] zonefs: document the explicit-open mount option
Date: Fri,  4 Sep 2020 20:23:28 +0900	[thread overview]
Message-ID: <20200904112328.28887-4-johannes.thumshirn@wdc.com> (raw)
In-Reply-To: <20200904112328.28887-1-johannes.thumshirn@wdc.com>

Document the newly introduced explicit-open mount option.

Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
---
 Documentation/filesystems/zonefs.rst | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/Documentation/filesystems/zonefs.rst b/Documentation/filesystems/zonefs.rst
index 6c18bc8ce332..ff8bc3634bad 100644
--- a/Documentation/filesystems/zonefs.rst
+++ b/Documentation/filesystems/zonefs.rst
@@ -326,6 +326,21 @@ discover the amount of data that has been written to the zone. In the case of a
 read-only zone discovered at run-time, as indicated in the previous section.
 The size of the zone file is left unchanged from its last updated value.
 
+A zoned block device (e.g. a NVMe Zoned Namespace device) may have
+limits on the number of zones that can be active, that is, zones that
+are in the the implicit open, explicit open or closed conditions.
+This potential limitation translate into a risk for applications to see
+write IO errors due to this limit being exceeded if the zone of a file
+is not already active when a write request is issued by the user.
+
+To avoid these potential errors, the "explicit-open" mount option
+forces zones to be made active using an open zone command when a file
+is open for writing for the first time. If the zone open command
+succeeds, the application is then guaranteed that write requests can be
+processed. Conversely, the "explicit-open" mount option will result in
+a zone close command being issued to the device on the last close() of
+a zone file if the zone is not full nor empty.
+
 Zonefs User Space Tools
 =======================
 
-- 
2.26.2


  parent reply	other threads:[~2020-09-04 11:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 11:23 [PATCH 0/3] zonefs: introduce -o " Johannes Thumshirn
2020-09-04 11:23 ` [PATCH 1/3] zonefs: introduce helper for zone management Johannes Thumshirn
2020-09-07  2:55   ` Damien Le Moal
2020-09-04 11:23 ` [PATCH 2/3] zonefs: open/close zone on file open/close Johannes Thumshirn
2020-09-07  3:06   ` Damien Le Moal
2020-09-07  8:49     ` Johannes Thumshirn
2020-09-07  9:52       ` Damien Le Moal
2020-09-07  4:32   ` Damien Le Moal
2020-09-04 11:23 ` Johannes Thumshirn [this message]
2020-09-04 15:17   ` [PATCH 3/3] zonefs: document the explicit-open mount option Randy Dunlap
2020-09-07  3:09   ` Damien Le Moal

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=20200904112328.28887-4-johannes.thumshirn@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --subject='Re: [PATCH 3/3] zonefs: document the explicit-open mount option' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).