public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Yi Zhang <yi.zhang@redhat.com>,
	"logang@deltatee.com" <logang@deltatee.com>,
	"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"sandeen@sandeen.net" <sandeen@sandeen.net>
Subject: Re: [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs
Date: Wed, 19 Oct 2022 06:16:03 +0000	[thread overview]
Message-ID: <122cec5e-5374-e98f-a8e7-b063d9c413fc@nvidia.com> (raw)
In-Reply-To: <20221019051244.810755-1-yi.zhang@redhat.com>

On 10/18/22 22:12, Yi Zhang wrote:
> The new minimum size for the xfs log is 64MB which introudced from
> xfsprogs v5.19.0, let's ignore it, or nvme/013 will be failed at:
> 

instead of removing it set to 64MB ?

-ck




  parent reply	other threads:[~2022-10-19  6:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  5:12 [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs Yi Zhang
2022-10-19  6:06 ` Chaitanya Kulkarni
2022-10-19  6:16 ` Chaitanya Kulkarni [this message]
2022-10-19 14:19   ` Eric Sandeen
2022-10-19 19:18     ` Chaitanya Kulkarni
2022-10-21  8:58       ` Shinichiro Kawasaki
2022-10-21 21:42         ` Chaitanya Kulkarni
2022-10-21 23:56           ` Shinichiro Kawasaki
2022-10-23 15:27             ` Yi Zhang
2022-10-24  0:50               ` Shinichiro Kawasaki
2022-10-24  6:32                 ` Yi Zhang
2022-10-24 10:31                   ` Shinichiro Kawasaki
2022-10-25  0:42                 ` Chaitanya Kulkarni
2022-10-25  1:53                   ` Shinichiro Kawasaki

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=122cec5e-5374-e98f-a8e7-b063d9c413fc@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sandeen@sandeen.net \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yi.zhang@redhat.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