Upcoming verifiers treat the unknown ro_compat flag written via xfs_db
as corruption, so use the -d flag to allow it, and filter our the
resulting informational message.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
# set the highest bit of features_ro_compat, use it as an unknown
# feature bit. If one day this bit become known feature, please
# change this case.
# set the highest bit of features_ro_compat, use it as an unknown
# feature bit. If one day this bit become known feature, please
# change this case.
-$XFS_DB_PROG -x -c "sb 0" -c "write features_ro_compat $((2**31))" $SCRATCH_DEV
+$XFS_DB_PROG -x -c "sb 0" -c "write -d features_ro_compat $((2**31))" \
+ $SCRATCH_DEV | grep -v "Allowing write of corrupted data"
# rw mount with unknown ro-compat feature should fail
echo "rw mount test"
# rw mount with unknown ro-compat feature should fail
echo "rw mount test"