From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Naohiro Aota <naohiro.aota@wdc.com>,
linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH v2] btrfs: zoned: move superblock logging zone location
Date: Fri, 9 Apr 2021 12:48:20 +0200 [thread overview]
Message-ID: <20210409104820.GQ7604@twin.jikos.cz> (raw)
In-Reply-To: <d22f8dfc-5ca4-4dab-2733-61563475a4a5@toxicpanda.com>
On Thu, Apr 08, 2021 at 10:57:32AM -0400, Josef Bacik wrote:
> On 4/8/21 4:25 AM, Naohiro Aota wrote:
> > confusion.
> >
> > Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
>
> Thanks Naohiro, this makes it much easier to understand,
>
> Reviewed-by: Josef Bacik <josef@toxicpanda.com>
>
> Dave, I know you're on vacation, this needs to go to Linus for this cycle so we
> don't have two different SB slots for two different kernels. I don't want to
> disturb your vacation, so I'll put this in a pull request tomorrow to Linus. If
> you already had plans to do this let me know and I'll hold off. Thanks,
We don't even have mkfs support for zoned filesystem merged so that the
format is not final was not an issue and that's why I did not hurry
pushing it in that cycle and I still rather not do that.
The design-level problem is the backup copy offset, that's been
discussed in some previous iteration - whether it's right to place all
copies under the first 1T or if we should spread them. For me this is
still not settled, I haven't read through all the replies and given it
enough thought.
That could lead to another change of the offsets that I'm sure we want
to avoid.
next prev parent reply other threads:[~2021-04-09 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:25 [PATCH v2] btrfs: zoned: move superblock logging zone location Naohiro Aota
2021-04-08 14:57 ` Josef Bacik
2021-04-09 10:48 ` David Sterba [this message]
2021-04-09 11:07 ` David Sterba
2021-04-10 9:29 ` David Sterba
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=20210409104820.GQ7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.