From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v4 3/4] zonefs: open/close zone on file open/close
Date: Fri, 11 Sep 2020 07:39:00 +0000 [thread overview]
Message-ID: <SN4PR0401MB3598940B9EC43330631FA2009B240@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: CY4PR04MB375116B70163C393E7F058D8E7240@CY4PR04MB3751.namprd04.prod.outlook.com
On 11/09/2020 07:11, Damien Le Moal wrote:
> I do not think it is about loosing data. If this type of error is repeated with
> the open zones left as is, you can end up with only these zones being writable
> and everything else read-only. So better take action and use the remount
> read-only big hammer right away rather than ending up in a weird FS state. So
> may be something like:
>
> /*
> * Leaving zones explicitly open may lead to a state
> * where most zones cannot be written (zone resources
> * exhausted). So take preventive action by remounting
> * read-only.
> */
Fixed
next prev parent reply other threads:[~2020-09-11 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 14:37 [PATCH v4 0/4] zonefs: introduce helper for zone management Johannes Thumshirn
2020-09-10 14:37 ` [PATCH v4 1/4] " Johannes Thumshirn
2020-09-10 14:37 ` [PATCH v4 2/4] zonefs: provide zonefs_io_error variant that can be called with i_truncate_mutex held Johannes Thumshirn
2020-09-11 5:05 ` Damien Le Moal
2020-09-11 7:52 ` Johannes Thumshirn
2020-09-10 14:37 ` [PATCH v4 3/4] zonefs: open/close zone on file open/close Johannes Thumshirn
2020-09-11 5:11 ` Damien Le Moal
2020-09-11 7:39 ` Johannes Thumshirn [this message]
2020-09-10 14:37 ` [PATCH v4 4/4] zonefs: document the explicit-open mount option Johannes Thumshirn
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=SN4PR0401MB3598940B9EC43330631FA2009B240@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).