mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
fc671750a5
The mount binary changed its output w.r.t. red-only devices, and stopped referring to a "block device." This broke at least test xfs/200; add a common filter to remove the "block device" from older mount binary output, and change the 200.out file to match. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Rich Johnston <rjohnston@sgi.com>
25 lines
894 B
Plaintext
25 lines
894 B
Plaintext
QA output created by 200
|
|
setting device read-only
|
|
mounting read-only block device:
|
|
mount: SCRATCH_DEV is write-protected, mounting read-only
|
|
touching file on read-only filesystem (should fail)
|
|
touch: cannot touch 'SCRATCH_MNT/foo': Read-only file system
|
|
unmounting read-only filesystem
|
|
setting device read-write
|
|
mounting read-write block device:
|
|
touch files
|
|
going down:
|
|
unmounting shutdown filesystem:
|
|
setting device read-only
|
|
mounting filesystem that needs recovery on a read-only device:
|
|
mount: SCRATCH_DEV is write-protected, mounting read-only
|
|
mount: cannot mount SCRATCH_DEV read-only
|
|
unmounting read-only filesystem
|
|
umount: SCRATCH_MNT: not mounted
|
|
mounting filesystem with -o norecovery on a read-only device:
|
|
mount: SCRATCH_DEV is write-protected, mounting read-only
|
|
unmounting read-only filesystem
|
|
setting device read-write
|
|
mounting filesystem that needs recovery with -o ro:
|
|
*** done
|