On 30/12/2021 20.25, Per Jessen wrote:
Carlos E. R. wrote:
On 30/12/2021 13.51, Andrei Borzenkov wrote:
On Wed, Dec 29, 2021 at 9:52 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
<0.4> 2021-12-29 12:43:12 minas-tirith kernel - - - [ 7297.208721] reiserfs: read-write mode is unsupported. <0.4> 2021-12-29 12:43:12 minas-tirith kernel - - - [ 7297.208724] reiserfs: load module with allow_unsupported=1 to enable read-write mode. ...
There you have, the log clearly says "read-write mode is unsupported", so
It even tells you exactly what you need to do to enable read-write.
I am aware.
Might have been better to reformulate the question - "to solve this problem, why should I do as my system suggests?" :-)
Yes, that is so.
this is intentional. It also says "load module with allow_unsupported=1 to enable read-write mode", but I don't know the consequences of doing that. The laptop might explode or eat my kittens.
Well, so do not. It is your decision.
No documentation.
With or without documentation, your laptop might still explode or eat your kittens.
Correct :-)
But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful.
And what dangers do I risk. Anyway, I'm already in the slow process of backing up the partition, with intent to reformat it as XFS, unless someone has a better proposal. And then, I have to repeat the process with my main desktop machine. [...] I forgot to click send on this yesterday. So, overnight the backup image was made (took 148 minutes, after the preparations to make space in the destination disk). This made, I can now reboot the machine and try r/w mode, but after that I will reformat the partition as decided. So if you want me to test something before I go ahead, say so ;-) If r/w works, why not use the partition as is? Well, because I already know of problems with reiserfs that now I know will never be corrected. Impossible to bugzilla about them. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)