xfstests: fixes for CRCs and small devices
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | xfs/033: add golden output for CRC enabled filesystemscommon/ tests/ tests/ | +207 | 1 reply | |
| 2/6 | xfs/189: noattr2 invalid for CRC enabled filesystemscommon/ tests/ | +12 | 1 reply | |
| 3/6 | generic/003: ensure time changes between stat callstests/ | +61 | 1 reply | |
| 4/6 | shared/051: CRC enabled filesystems handle more than 25 ACLstests/ | +16 | 1 reply | |
| 5/6 | xfs/217: prevent enospc failures on small test devicestests/ | +4 | 1 reply | |
| 6/6 | xfs/167: need at least 10GB of scratch space to runtests/ | +6 | 1 reply |
Reviews trailers per patch
5 of 6 patches have a Reviewed-by or Acked-by.
| Patch | Christoph Hellwig |
|---|---|
| 1/6 | R-b |
| 2/6 | R-b |
| 3/6 | R-b |
| 4/6 | |
| 5/6 | R-b |
| 6/6 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/6] xfstests: fixes for CRCs and small devices
Hi folks,
The following set of patches fix two sets of issues. The first is that small, fast filesystems like on a ramdisk trigger some interesting failures due to the rate of modification being so high on such devices. Hence we can do things like run a small filesystem out of space in a few seconds, whereas it woul dtake a few minutes on a SSD or spinning disk. Hence some tests require some small tweaks to avoid failures in such situations.
The second set of patches continue the work of fixing test failures on CRC enabled filesystems due to issues with the tests themselves. There are stll more test fixes needed, but I'm now down to single digit failure rates on CRC enabled filesystems with these patches.
Cheers,
Dave.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs