mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Eric Sandeen
f4eee51260
xfs/111 is failing today, primarily because it obliterates the root inode chunk and the verifiers fail the mount - i.e. the test fails to properly test the thing it's meant to test. Change the test so that the induced corruption is further into the filesystem, but still hitting the inodes which have been created for the test, so that the fs can mount and continue. This requires that the helper binary (itrash) take an offset, which we will figure out by using xfs_db. This changes the locations of the inodes we hit; we're not really going to be able to predict that terribly well, so remove the output which shows inode offsets, and just keep track of whether we managed to obliterate any at all. The test still fails, because the fs is corrupted; this was done intentionally, so run xfs_repair before the test exits to fix things up. (This test doesn't run often; it's not in the auto group, and all the failures are extremely noisy and time consuming...) Signed-off-by: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Brian Foster <bfoster@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
14 lines
401 B
Plaintext
14 lines
401 B
Plaintext
QA output created by 111
|
|
meta-data=DDEV isize=XXX agcount=N, agsize=XXX blks
|
|
data = bsize=XXX blocks=XXX, imaxpct=PCT
|
|
= sunit=XXX swidth=XXX, unwritten=X
|
|
naming =VERN bsize=XXX
|
|
log =LDEV bsize=XXX blocks=XXX
|
|
realtime =RDEV extsz=XXX blocks=XXX, rtextents=XXX
|
|
Create some files
|
|
Blat inode clusters
|
|
Starting overwrite
|
|
Overwrite complete
|
|
Attempting bulkstat
|
|
SCRATCH_MNT start inode=0
|