From: Dave Chinner <dchinner@xxxxxxxxxx> Lastest XFS kernel makes the superblock bad magic number error message more meaningful, and that's being picked up by xfsprogs in very short order. And, of course, the error is output by xfs_repair, too, and it's been captured in the golden output of a test. Fix it by filtering the output back down to the old message. Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> --- common/repair | 1 + 1 file changed, 1 insertion(+) diff --git a/common/repair b/common/repair index 5a957f4e..463ef9db 100644 --- a/common/repair +++ b/common/repair @@ -90,6 +90,7 @@ s/(superblock) (\d+)/\1 AGNO/; s/(AG \#)(\d+)/\1AGNO/; s/(reset bad sb for ag) (\d+)/\1 AGNO/; s/(unknown block state, ag )(\d+)(, blocks? )(\d+)/\1AGNO\3AGBNO/; +s/^Superblock has (bad magic number) 0x.*/\1/; /^Note - quota info will be regenerated on next quota mount.$/ && next; print;' } -- 2.35.1
