On 23/8/23 13:05, Donald Douwsma wrote:
On 2/8/23 19:41, Carlos Maiolino wrote:
Hello.
The xfsprogs for-next branch, located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/refs/?h=for-next
Has just been updated.
Patches often get missed, so if your outstanding patches are properly
reviewed on
the list and not included in this update, please let me know.
Its a minor one, but the unit test for xfs_repair progress reporting[1]
depends on
xfs_repair: always print an estimate when reporting progress
https://lore.kernel.org/linux-xfs/20230531064143.1737591-1-ddouwsma@xxxxxxxxxx/
[1] [PATCH v4] xfstests: add test for xfs_repair progress reporting
https://lore.kernel.org/linux-xfs/20230610063855.gg6cd7bh5pzyobhe@zlang-mailbox/
The new head of the for-next branch is commit:
a86308c98d33e921eb133f47faedf1d9e62f2e77
2 new commits:
Bill O'Donnell (1):
[780e93c51] mkfs.xfs.8: correction on mkfs.xfs manpage since
reflink and dax are compatible
Mmm, this reminds me, sparse inodes have been the default for a while
now, I thought someone was going to submit a patch to update the
manpage, but I cant see it anywhere.
Nevermind, it was in 6.3
[965f91091] mkfs: fix man's default value for sparse option
- Don
Wu Guanghao (1):
[a86308c98] xfs_repair: fix the problem of repair failure
caused by dirty flag being abnormally set on buffer
Code Diffstat:
man/man8/mkfs.xfs.8.in | 7 -------
repair/scan.c | 2 +-
2 files changed, 1 insertion(+), 8 deletions(-)
