Joanne, On 10/29/25 17:34, Joanne Chang wrote: > Currently, the created files are filled with 0. When filesystem level > compression is used, they take up much less space than expected. So > the final fallocate does not show an error. > > The created files are filled by /dev/urandom instead to ensure they > are not compressed. This way the files take up the same space whether > compression is used or not. > > Signed-off-by: Joanne Chang <[email protected]> > --- > tests/f2fs/011 | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/tests/f2fs/011 b/tests/f2fs/011 > index c21cb586..75679b36 100755 > --- a/tests/f2fs/011 > +++ b/tests/f2fs/011 > @@ -35,8 +35,9 @@ _scratch_mount -o checkpoint=disable:10% > pinfile=$SCRATCH_MNT/file > > # simulate fragment status in f2fs > -for ((i=0;i<256;i++)) do > - $XFS_IO_PROG -f -c "pwrite 0 1m" $SCRATCH_MNT/$i >>$seqres.full > +dd if=/dev/urandom of=$SCRATCH_MNT/0 bs=1M count=1 2> /dev/null
IIRC, $XFS_IO_PROG is preferred in xfstests [1] [1] https://lore.kernel.org/fstests/20250326140938.6ll7yeez6iwab...@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com So, what do you think of this? for ((i=0;i<256;i++)) do $XFS_IO_PROG -f -c "pwrite -i /dev/urandom 0 1m" $SCRATCH_MNT/$i >>$seqres.full done > +for ((i=1;i<256;i++)) do > + cp $SCRATCH_MNT/0 $SCRATCH_MNT/$i > done > sync > _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
