linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Anand Jain <anand.jain@oracle.com>,
	Naohiro Aota <Naohiro.Aota@wdc.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	David Sterba <dsterba@suse.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	Nikolay Borisov <nborisov@suse.com>,
	Matias Bjorling <Matias.Bjorling@wdc.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Hannes Reinecke <hare@suse.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v3 03/27] btrfs: Check and enable HMZONED mode
Date: Sat, 17 Aug 2019 00:05:07 +0000	[thread overview]
Message-ID: <BYAPR04MB5816C9F8F5D36B492B33AFB4E7AE0@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: 86ef7944-0029-3d61-0ae3-874015726751@oracle.com

On 2019/08/16 16:57, Anand Jain wrote:
> 
> 
> On 8/16/19 10:23 PM, Damien Le Moal wrote:
>> On 2019/08/15 22:46, Anand Jain wrote:
>>> On 8/8/19 5:30 PM, Naohiro Aota wrote:
>>>> HMZONED mode cannot be used together with the RAID5/6 profile for now.
>>>> Introduce the function btrfs_check_hmzoned_mode() to check this. This
>>>> function will also check if HMZONED flag is enabled on the file system and
>>>> if the file system consists of zoned devices with equal zone size.
>>>>
>>>> Additionally, as updates to the space cache are in-place, the space cache
>>>> cannot be located over sequential zones and there is no guarantees that the
>>>> device will have enough conventional zones to store this cache. Resolve
>>>> this problem by disabling completely the space cache.  This does not
>>>> introduces any problems with sequential block groups: all the free space is
>>>> located after the allocation pointer and no free space before the pointer.
>>>> There is no need to have such cache.
>>>>
>>>> For the same reason, NODATACOW is also disabled.
>>>>
>>>> Also INODE_MAP_CACHE is also disabled to avoid preallocation in the
>>>> INODE_MAP_CACHE inode.
>>>
>>>    A list of incompatibility features with zoned devices. This need better
>>>    documentation, may be a table and its reason is better.
>>
>> Are you referring to the format of the commit message itself ? Or would you like
>> to see a documentation added to Documentation/filesystems/btrfs.txt ?
> 
>   Documenting in the commit change log is fine. But it can be better
>   documented in a listed format as it looks like we have a list of
>   features which will be incompatible with zoned devices.

OK. We can update btrfs.txt doc file.

> 
> more below..
[...]>>>> +	if (!hmzoned_devices && incompat_hmzoned) {
>>>> +		/* No zoned block device found on HMZONED FS */
>>>> +		btrfs_err(fs_info, "HMZONED enabled file system should have zoned devices");
>>>> +		ret = -EINVAL;
>>>> +		goto out;
>>>
>>>
>>>    When does the HMZONED gets enabled? I presume during mkfs. Where are
>>>    the related btrfs-progs patches? Searching for the related btrfs-progs
>>>    patches doesn't show up anything in the ML. Looks like I am missing
>>>    something, nor the cover letter said anything about the progs part.
> 
> 
>   Any idea about this comment above?

Yep, the feature is set at format time if some of the devices in the volume are
zoned. The btrfs-progs changes to handle that are ready too.

Naohiro, please re-post btrfs-progs too !

> 
> Thanks, Anand

-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2019-08-17  0:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  9:30 [PATCH v3 00/27] btrfs zoned block device support Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 01/27] btrfs: introduce HMZONED feature flag Naohiro Aota
2019-08-16  4:49   ` Anand Jain
2019-08-08  9:30 ` [PATCH v3 02/27] btrfs: Get zone information of zoned block devices Naohiro Aota
2019-08-16  4:44   ` Anand Jain
2019-08-16 14:19     ` Damien Le Moal
2019-08-16 23:47       ` Anand Jain
2019-08-16 23:55         ` Damien Le Moal
2019-08-08  9:30 ` [PATCH v3 03/27] btrfs: Check and enable HMZONED mode Naohiro Aota
2019-08-16  5:46   ` Anand Jain
2019-08-16 14:23     ` Damien Le Moal
2019-08-16 23:56       ` Anand Jain
2019-08-17  0:05         ` Damien Le Moal [this message]
2019-08-20  5:07         ` Naohiro Aota
2019-08-20 13:05           ` David Sterba
2019-08-08  9:30 ` [PATCH v3 04/27] btrfs: disallow RAID5/6 in " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 05/27] btrfs: disallow space_cache " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 06/27] btrfs: disallow NODATACOW " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 07/27] btrfs: disable tree-log " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 08/27] btrfs: disable fallocate " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 09/27] btrfs: align device extent allocation to zone boundary Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 10/27] btrfs: do sequential extent allocation in HMZONED mode Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 11/27] btrfs: make unmirroed BGs readonly only if we have at least one writable BG Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 12/27] btrfs: ensure metadata space available on/after degraded mount in HMZONED Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 13/27] btrfs: reset zones of unused block groups Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 14/27] btrfs: limit super block locations in HMZONED mode Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 15/27] btrfs: redirty released extent buffers in sequential BGs Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 16/27] btrfs: serialize data allocation and submit IOs Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 17/27] btrfs: implement atomic compressed IO submission Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 18/27] btrfs: support direct write IO in HMZONED Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 19/27] btrfs: serialize meta IOs on HMZONED mode Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 20/27] btrfs: wait existing extents before truncating Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 21/27] btrfs: avoid async checksum/submit on HMZONED mode Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 22/27] btrfs: disallow mixed-bg in " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 23/27] btrfs: disallow inode_cache " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 24/27] btrfs: support dev-replace " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 25/27] btrfs: enable relocation " Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 26/27] btrfs: relocate block group to repair IO failure in HMZONED Naohiro Aota
2019-08-08  9:30 ` [PATCH v3 27/27] btrfs: enable to mount HMZONED incompat flag Naohiro Aota

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=BYAPR04MB5816C9F8F5D36B492B33AFB4E7AE0@BYAPR04MB5816.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=Matias.Bjorling@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=anand.jain@oracle.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=hare@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nborisov@suse.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).