From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Tim Walker <timtwalker@outlook.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [question] ZBC/ZAC Offline/read-only zone support
Date: Tue, 14 Apr 2020 07:09:03 -0700 [thread overview]
Message-ID: <20200414140903.GB69282@google.com> (raw)
In-Reply-To: <BN6PR02MB3379134F5821A8D6995E3084DEDA0@BN6PR02MB3379.namprd02.prod.outlook.com>
On 04/14, Tim Walker wrote:
> Hello-
>
> I am trying to determine how f2fs handles an offline (or read-only) zone when it is backed by a host-managed SMR HDD. I haven't been able to find any specific code path that places an offline zone into a separate list, or a path that checks the zone condition. Do we support a zone going read-only or offline? Thanks for the info.
Which scenario do we need to see ro or offline zones? Can we expect some
when mounting the filesystem? Or, does setting a zone to readonly happen
in runtime? If we detect them at mount time like former one, we need to
treat the discarded blocks in the zone with unusable space, and set
allocation bits to avoid GC.
>
> Best regards,
> Tim Walker
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-04-14 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 4:23 [f2fs-dev] [question] ZBC/ZAC Offline/read-only zone support Tim Walker
2020-04-14 11:50 ` Chao Yu
2020-04-15 2:54 ` Tim Walker
2020-04-15 7:15 ` Chao Yu
2020-04-14 14:09 ` Jaegeuk Kim [this message]
2020-04-15 2:49 ` Tim Walker
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=20200414140903.GB69282@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=timtwalker@outlook.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;
as well as URLs for NNTP newsgroup(s).