From: Chandan Babu R <chandan.babu@oracle.com>
To: david@fromorbit.com
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/5] xfsprogs: Large extent counters
Date: Wed, 25 May 2022 15:06:24 +0530 [thread overview]
Message-ID: <871qwiar5g.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20220525053630.734938-1-chandan.babu@oracle.com>
On Wed, May 25, 2022 at 11:06:25 AM +0530, Chandan Babu R wrote:
> This patchset implements the changes to userspace programs that are
> required to support large per-inode extent counters. These changes
> allow programs in xfsprogs to be able to create and work with
> filesystem instances with 64-bit data fork extent counter and 32-bit
> attr fork extent counter fields.
>
> The patchset can also be obtained from
> https://github.com/chandanr/xfsprogs-dev.git at branch
> large-extent-counters.
>
> PS: Dave, I noticed that xfs/070 is failing during xfstest runs. This
> failure is seen on libxfs-5.19-sync branch as well. The bad commit was
> "xfs: validate v5 feature fields". I will debug this and find the root
> cause.
The failure is due to the above mentioned patch changing the warning message
printed (in xfs_validate_sb_common()) when an invalid superblock magic number
is detected.
--
chandan
prev parent reply other threads:[~2022-05-25 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 5:36 [PATCH 0/5] xfsprogs: Large extent counters Chandan Babu R
2022-05-25 5:36 ` [PATCH 1/5] xfs_repair: check filesystem geometry before allowing upgrades Chandan Babu R
2022-06-22 18:57 ` Eric Sandeen
2022-06-22 22:12 ` Darrick J. Wong
2022-05-25 5:36 ` [PATCH 2/5] xfsprogs: Invoke bulkstat ioctl with XFS_BULK_IREQ_NREXT64 flag Chandan Babu R
2022-05-25 5:36 ` [PATCH 3/5] xfs_info: Report NREXT64 feature status Chandan Babu R
2022-05-25 5:36 ` [PATCH 4/5] mkfs: Add option to create filesystem with large extent counters Chandan Babu R
2022-05-25 5:36 ` [PATCH 5/5] xfs_repair: Add support for upgrading to " Chandan Babu R
2022-05-25 9:36 ` Chandan Babu R [this message]
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=871qwiar5g.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@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