On Thu, Dec 05, 2024 at 07:40:15AM -0800, Darrick J. Wong wrote: > On Thu, Dec 05, 2024 at 11:29:20PM +0800, Zorro Lang wrote: > > Hi, > > > > Recently all my 64k blocksize xfs tests fail [1] on latest mainline > > linux (HEAD=feffde684ac29a3b7aec82d2df850fbdbdee55e4) with > > latest xfsprogs (for-next branch, HEAD=409477af). Do I miss something? > > Most probably this: > https://lore.kernel.org/linux-xfs/Z0l5OezlOv7QGCeT@xxxxxxxxxxxxx/T/#m0e8676370031255c7b198565d34ae597cef908bc Great! Thanks for your quick response. This regression cause LBS test fail, I'll skip LBS test temporarily. Thanks, Zorro > > --D > > > Thanks, > > Zorro > > > > [1] > > # mkfs.xfs -f -b size=65536 /dev/nvme0n1p5 > > meta-data=/dev/nvme0n1p5 isize=512 agcount=4, agsize=61440 blks > > = sectsz=512 attr=2, projid32bit=1 > > = crc=1 finobt=1, sparse=1, rmapbt=1 > > = reflink=1 bigtime=1 inobtcount=1 nrext64=1 > > = exchange=0 > > data = bsize=65536 blocks=245760, imaxpct=25 > > = sunit=0 swidth=0 blks > > naming =version 2 bsize=65536 ascii-ci=0, ftype=1, parent=0 > > log =internal log bsize=65536 blocks=32608, version=2 > > = sectsz=512 sunit=0 blks, lazy-count=1 > > realtime =none extsz=65536 blocks=0, rtextents=0 > > Discarding blocks...Done. > > > > # mount -t xfs /dev/nvme0n1p5 /mnt/test > > mount: /mnt/xfstests/test: wrong fs type, bad option, bad superblock on /dev/nvme0n1p5, missing codepage or helper program, or other error. > > dmesg(1) may have more information after failed mount system call. > > > > # dmesg > > [ 459.450856] XFS (nvme0n1p5): Sparse inode alignment (0) is invalid. > > [ 459.458090] XFS (nvme0n1p5): SB validate failed with error -22. > > > > >
