mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Dave Chinner
86c1b5588c
xfs/042 is really an xfs_fsr test, and it only writes about 60MB of data. however, because it is trying to write lots of data in ENOSPC conditions, it can take a long time as XFS does flushes to maximise space usage at ENOSPC. e.g. on a slow 1p VM: xfs/042 426s ... 425s It takes a long time to write a small amount of data. To avoid this slow flushing problem, create the fragmented files with fallocate() rather than write(), which fails much faster as there is no dirty data to flush before retrying the allocation and failing. THis results in: xfs/042 425s ... 11s A massive reduction in runtime, such that we can consider putting xfs/042 into the quick group.... Signed-off-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
13 lines
417 B
Plaintext
13 lines
417 B
Plaintext
QA output created by 042
|
|
Make a 48 megabyte filesystem on SCRATCH_DEV and mount... done
|
|
Reserve 16 1Mb unfragmented regions... done
|
|
Fill filesystem with fill file... done
|
|
Use up any further available space... done
|
|
Punch every second 4k block... done
|
|
Create one very large file... done
|
|
Remove other files... done
|
|
Run xfs_fsr on filesystem... done
|
|
Check fill file... done
|
|
Check large file... done
|
|
xfs_fsr tests passed.
|