mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Lukas Czerner
3c9b1fe59e
We should never be able to mount ext4 file system read-write with read-only external journal device. Test it. This problem has been addressed with proposed kernel patch https://lore.kernel.org/linux-ext4/20200717090605.2612-1-lczerner@redhat.com/ The test was based on generic/050. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Reviewed-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Eryu Guan <guaneryu@gmail.com>
33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
QA output created by 002
|
|
setting log device read-only
|
|
mounting with read-only log 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 log device read-write
|
|
mounting with read-write log device:
|
|
touch files
|
|
going down:
|
|
unmounting shutdown filesystem:
|
|
setting log device read-only
|
|
mounting filesystem that needs recovery with a read-only log 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 with a read-only log device:
|
|
mount: SCRATCH_MNT: wrong fs type, bad option, bad superblock on SCRATCH_DEV, missing codepage or helper program, or other error
|
|
unmounting read-only filesystem
|
|
umount: SCRATCH_DEV: not mounted
|
|
setting fs device read-only
|
|
mounting filesystem with -o norecovery with a read-only fs and log device:
|
|
mount: device write-protected, mounting read-only
|
|
unmounting read-only filesystem
|
|
setting fs device read-write
|
|
mounting filesystem with -o norecovery,ro with a read-only log device:
|
|
unmounting read-only filesystem
|
|
setting log device read-write
|
|
mounting filesystem that needs recovery with -o ro:
|
|
*** done
|