mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Eryu Guan
69854f8dc5
util-linux commit 6dede2f2f7c5 ("libmount: support MS_RDONLY on
write-protected devices") changed the error message on read-only
block device, and in the failure case printed one line message
instead of two (for details please see comments in common/filter),
and this change broke generic/050 and overlay/035.
Fix it by adding more filter rules to _filter_ro_mount and updating
associated .out files to unify the output from both old and new
util-linux versions.
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
25 lines
865 B
Plaintext
25 lines
865 B
Plaintext
QA output created by 050
|
|
setting device read-only
|
|
mounting read-only block device:
|
|
mount: device 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: device write-protected, mounting read-only
|
|
mount: cannot mount device read-only
|
|
unmounting read-only filesystem
|
|
umount: SCRATCH_DEV: not mounted
|
|
mounting filesystem with -o norecovery on a read-only device:
|
|
mount: device write-protected, mounting read-only
|
|
unmounting read-only filesystem
|
|
setting device read-write
|
|
mounting filesystem that needs recovery with -o ro:
|
|
*** done
|