Bugzilla – Bug 1215158
reiserfs mount wrongly claims block device is read-only
Last modified: 2023-09-22 09:47:16 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: I created new reiserfs filesystems with mkfs.reiserfs 3.6.27 on a 931.51 GiB /dev/bcache3 device (with LUKS-encrypted /dev/sde1 as backing device) as well as a 117.19 GiB /dev/loop0 device (created with losetup --find --show from a sparse file on btrfs) and mount insists they are read-only. Reproducible: Always Steps to Reproduce: 1. select or create a block device for this test with reasonable size for the time when reiserfs was popular, e.g. 120 GB 2. create reiserfs on device 3. try to mount it Actual Results: In both cases, mount reports mount: /mnt/old: WARNING: source write-protected, mounted read-only. The filesystem is read-only and cannot be remounted rw. Manually writing the the block device, e.g. /dev/loop0, and reading from it confirms that the block device can be written to and retains the written information. Expected Results: The filesystem is mounted rw. If this is a safety feature for a filesytem deemed obsolete, the error message should clarify this. mkfs.reiserfs 3.6.27 kernel 5.14.21-150500.55.19-default
starting from SLE15 reiserfs has been unsupported: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/index.html#fate-323394 from dmesg when trying to mount a reiserfs partition: > [ 65.317809] reiserfs: read-write mode is unsupported. > [ 65.317812] reiserfs: load module with allow_unsupported=1 to enable read-write mode. so you can do: > echo Y > /sys/module/reiserfs/parameters/allow_unsupported after which you will be able to mount the partition rw.