Files
apfstests/242.out
T
Alex Elder 9935bd9855 xfstests: coalesce contiguous extents in extent map output
The specific set of extent sizes allocated to a file is not always
deterministic.  In particular, sometimes a range of unwritten blocks
is covered by a single extent, while in other cases it might be
represented by multiple consecutive unwritten extents.  This can
result in spurious errors being reported in tests that check file
extent maps.

Add a filter that finds adjacent extents in what gets produced for
fiemap and bmap output and coalesces them as if all consective
extents of the same time were really just one extent.  (Note that
as implemented here this applies to all extent types, not just
unwritten extents.)

Update the golden output for test 242 to reflect the change.

Signed-off-by: Alex Elder <aelder@sgi.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
2011-04-29 16:20:22 -05:00

50 lines
996 B
Plaintext

QA output created by 242
1. into a hole
0: [0..7]: hole
1: [8..23]: unwritten
2: [24..39]: hole
2. into allocated space
0: [0..7]: data
1: [8..23]: unwritten
2: [24..39]: data
3. into unwritten space
0: [0..39]: unwritten
4. hole -> data
0: [0..7]: hole
1: [8..23]: unwritten
2: [24..31]: data
3: [32..39]: hole
5. hole -> unwritten
0: [0..7]: hole
1: [8..31]: unwritten
2: [32..39]: hole
6. data -> hole
0: [0..7]: data
1: [8..23]: unwritten
2: [24..39]: hole
7. data -> unwritten
0: [0..7]: data
1: [8..31]: unwritten
2: [32..39]: hole
8. unwritten -> hole
0: [0..23]: unwritten
1: [24..39]: hole
9. unwritten -> data
0: [0..23]: unwritten
1: [24..31]: data
2: [32..39]: hole
10. hole -> data -> hole
0: [0..7]: hole
1: [8..31]: unwritten
2: [32..39]: hole
11. data -> hole -> data
0: [0..7]: data
1: [8..31]: unwritten
2: [32..39]: data
12. unwritten -> data -> unwritten
0: [0..39]: unwritten
13. data -> unwritten -> data
0: [0..7]: data
1: [8..31]: unwritten
2: [32..39]: data