[oS-en] Leap 15.3: can't mount /home
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Unknown filesystem 'reiserfs' :-/ - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYcvG+hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVeQcAn1pPUk98DaNg71a+xWkt aO8+J/NUAJ9+K6U01YofXopVhWGaPh6VIt2Ygw== =nhEU -----END PGP SIGNATURE-----
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Wed, 29 Dec 2021 03:24:57 +0100 (CET) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Unknown filesystem 'reiserfs' :-/ root@orion> zypper search reiser Loading repository data... Reading installed packages... S | Name | Summary | Type --+--------------------------+------------------------------------------+-------- | libreiser4-1_2-1 | Reiser4 filesystem library | package | libreiser4-minimal-1_2-1 | Minimal version of the Reiser4 filesys-> | package | libreiserfs-0_3-0 | ReiserFS File System Access Library | package | libreiserfs-0_3-0-32bit | ReiserFS File System Access Library | package | libreiserfs-devel | ReiserFS Filesystem Access Tools | package | libreiserfs-devel-32bit | ReiserFS Filesystem Access Tools | package | libreiserfs-progs | ReiserFS Filesystem Access Tools | package | libreiserfscore-devel | Reiser File System Core Library Develo-> | package | libreiserfscore0 | Reiser File System Core Library | package | reiser4progs | Utilities for Managing the Reiser4 Fil-> | package | reiser4progs-devel | Header C files and static libs for the-> | package | reiserfs | Reiser File System utilities | package | reiserfs-kmp-azure | Reiserfs kernel module | package | reiserfs-kmp-default | Reiserfs kernel module | package | reiserfs-kmp-preempt | Reiserfs kernel module | package | reiserfs-kmp-rt | Reiserfs kernel module | package | reiserfs-kmp-rt_debug | Reiserfs kernel module | package root@orion> -- Bob Rogers http://www.rgrjr.com/
On 29/12/2021 04.29, Bob Rogers wrote:
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Wed, 29 Dec 2021 03:24:57 +0100 (CET)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Unknown filesystem 'reiserfs'
:-/
root@orion> zypper search reiser Loading repository data... Reading installed packages...
S | Name | Summary | Type --+--------------------------+------------------------------------------+-------- | libreiser4-1_2-1 | Reiser4 filesystem library | package | libreiser4-minimal-1_2-1 | Minimal version of the Reiser4 filesys-> | package | libreiserfs-0_3-0 | ReiserFS File System Access Library | package | libreiserfs-0_3-0-32bit | ReiserFS File System Access Library | package | libreiserfs-devel | ReiserFS Filesystem Access Tools | package | libreiserfs-devel-32bit | ReiserFS Filesystem Access Tools | package | libreiserfs-progs | ReiserFS Filesystem Access Tools | package | libreiserfscore-devel | Reiser File System Core Library Develo-> | package | libreiserfscore0 | Reiser File System Core Library | package | reiser4progs | Utilities for Managing the Reiser4 Fil-> | package | reiser4progs-devel | Header C files and static libs for the-> | package | reiserfs | Reiser File System utilities | package | reiserfs-kmp-azure | Reiserfs kernel module | package | reiserfs-kmp-default | Reiserfs kernel module | package | reiserfs-kmp-preempt | Reiserfs kernel module | package | reiserfs-kmp-rt | Reiserfs kernel module | package | reiserfs-kmp-rt_debug | Reiserfs kernel module | package root@orion>
Thanks. libreiserfs-0_3-0, libreiserfscore0 and reiserfs are already installed. But the kernel modules are not. [...] Ok, I installed "reiserfs-kmp-default", and now I can mount /home, but only partially (hand copied messages): mount: /home: WARNING: source write-protected, mount read only. mount: /dev/sda8 mounted on /home I see permissions of device are brw-rw----, I don't understand. Damn it, on syslog it says that read-write mode is not supported. This is intentional boicot by SUSE/openSUSE :-/ -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
Ok, I installed "reiserfs-kmp-default", and now I can mount /home, but only partially (hand copied messages):
mount: /home: WARNING: source write-protected, mount read only. mount: /dev/sda8 mounted on /home
I see permissions of device are brw-rw----, I don't understand.
Damn it, on syslog it says that read-write mode is not supported. This is intentional boicot by SUSE/openSUSE :-/
Maybe it is just a module option? -- Per Jessen, Zürich (8.4°C)
On Wed, Dec 29, 2021 at 6:24 PM Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
Ok, I installed "reiserfs-kmp-default", and now I can mount /home, but only partially (hand copied messages):
mount: /home: WARNING: source write-protected, mount read only.
This means the device is write protected.
mount: /dev/sda8 mounted on /home
I see permissions of device are brw-rw----, I don't understand.
Permissions of device nodes have absolutely nothing to do with the state of the underlying devices. Show full dmesg output.
Damn it, on syslog it says that read-write mode is not supported. This
Who says it? What it says? You do realize that it is impossible to comment on such statements?
is intentional boicot by SUSE/openSUSE :-/
Do you intend to start flamewar?
Maybe it is just a module option? Otherwise exact log message is needed.
"Source write protected" means device is write protected.
From: Andrei Borzenkov <arvidjaar@gmail.com> Date: Wed, 29 Dec 2021 19:12:44 +0300 On Wed, Dec 29, 2021 at 6:24 PM Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
Damn it, on syslog it says that read-write mode is not supported. This
Who says it? What it says? You do realize that it is impossible to comment on such statements?
is intentional boicot by SUSE/openSUSE :-/
Do you intend to start flamewar?
Maybe it is just a module option? Otherwise exact log message is needed.
"Source write protected" means device is write protected. From https://software.opensuse.org/package/reiserfs: reiserfs Reiser File System utilities This package includes utilities for making the file system (mkreiserfs), checking for consistency (reiserfsck), and resizing (resize_reiserfs). There is no official package available for openSUSE Leap 15.3 So it seems they want you to be able to read your reiserfs partitions in order to turn them into something else, but not to keep them running as such. -- Bob Rogers http://www.rgrjr.com/
On 29/12/2021 18.41, Bob Rogers wrote:
From: Andrei Borzenkov <arvidjaar@gmail.com> Date: Wed, 29 Dec 2021 19:12:44 +0300
On Wed, Dec 29, 2021 at 6:24 PM Per Jessen <per@computer.org> wrote: > > Carlos E. R. wrote: > > > > > Damn it, on syslog it says that read-write mode is not supported. This
Who says it? What it says? You do realize that it is impossible to comment on such statements?
> > is intentional boicot by SUSE/openSUSE :-/ >
Do you intend to start flamewar?
> Maybe it is just a module option? Otherwise exact log message is needed. >
"Source write protected" means device is write protected.
From https://software.opensuse.org/package/reiserfs:
reiserfs Reiser File System utilities
This package includes utilities for making the file system (mkreiserfs), checking for consistency (reiserfsck), and resizing (resize_reiserfs).
There is no official package available for openSUSE Leap 15.3
So it seems they want you to be able to read your reiserfs partitions in order to turn them into something else, but not to keep them running as such.
Shouldn't something as crucial as this be included in the release notes? Now I have a laptop that is not fully running, with a failed upgrade, and in which to convert a partition, which is an operation that takes a full day. (backup, reformat, restore, from external disk via USB 2, with rsync -c) And decide what filesystem to use instead of reiserfs, a decision that I had postponed till Leap 16 and that I'm now forced to take unawares. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-12-29 at 19:12 +0300, Andrei Borzenkov wrote:
On Wed, Dec 29, 2021 at 6:24 PM Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
Ok, I installed "reiserfs-kmp-default", and now I can mount /home, but only partially (hand copied messages):
mount: /home: WARNING: source write-protected, mount read only.
This means the device is write protected.
mount: /dev/sda8 mounted on /home
I see permissions of device are brw-rw----, I don't understand.
Permissions of device nodes have absolutely nothing to do with the state of the underlying devices. Show full dmesg output.
Since what point, the entire session?
Damn it, on syslog it says that read-write mode is not supported. This
Who says it? What it says? You do realize that it is impossible to comment on such statements?
Syslog says it. I could not paste actual output, ssh was not working when I posted, I could not mount necessary partitions. I simply hand copied the gist of the syslog message. And I still can't, network is not running (there are needed scipts in /usr/local/ which is not not mounted). I may try rebooting, now that /home mounts read only, and try. Otherwise, I can try an USB stick, but I can not login as user, only as root.
is intentional boicot by SUSE/openSUSE :-/
Do you intend to start flamewar?
No, but I'm quite pissed and disturbed :-/ Don't you realize I am hurt?
Maybe it is just a module option? Otherwise exact log message is needed.
"Source write protected" means device is write protected.
It is not. The disk is the same as the root, so it is not a hardware problem. [...] Ok, rebooted, I have network now. minas-tirith:~ # mount | grep reiserfs /dev/sda8 on /home type reiserfs (ro,relatime,user_xattr,acl) /dev/sda8 on /usr/local type reiserfs (ro,relatime,user_xattr,acl) /dev/sda8 on /var/spool/news type reiserfs (ro,relatime,user_xattr,acl) minas-tirith:~ # read only. Let's check syslog. minas-tirith:~ # grep "reiserfs" /var/log/messages <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - erase libreiserfscore0-3.6.27-lp152.3.8.x86_64: success <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - install libreiserfscore0-3.6.27-2.24.x86_64: success <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - erase libreiserfscore0-3.6.27-lp152.3.8.x86_64: success <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - install libreiserfscore0-3.6.27-2.24.x86_64: success <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - erase libreiserfs-0_3-0-0.3.0.5-lp152.3.5.x86_64: success <1.5> 2021-12-29 00:58:52 minas-tirith RPM - - install libreiserfs-0_3-0-0.3.0.5-1.30.x86_64: success <1.5> 2021-12-29 00:58:53 minas-tirith RPM - - erase libreiserfs-0_3-0-0.3.0.5-lp152.3.5.x86_64: success <1.5> 2021-12-29 00:58:53 minas-tirith RPM - - install libreiserfs-0_3-0-0.3.0.5-1.30.x86_64: success <1.5> 2021-12-29 01:07:59 minas-tirith RPM - - erase reiserfs-3.6.27-lp152.3.8.x86_64: success <1.5> 2021-12-29 01:07:59 minas-tirith RPM - - install reiserfs-3.6.27-2.24.x86_64: success <1.5> 2021-12-29 01:07:59 minas-tirith RPM - - erase reiserfs-3.6.27-lp152.3.8.x86_64: success <1.5> 2021-12-29 01:07:59 minas-tirith RPM - - install reiserfs-3.6.27-2.24.x86_64: success <1.5> 2021-12-29 03:21:29 minas-tirith 50mounted-tests - - - debug: mounted using GRUB reiserfs filesystem driver <1.5> 2021-12-29 12:41:42 minas-tirith RPM - - install reiserfs-kmp-default-5.3.18-59.37.2.x86_64: success <1.5> 2021-12-29 12:42:07 minas-tirith 50mounted-tests - - - debug: mounted using GRUB reiserfs filesystem driver <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. <0.5> 2021-12-29 12:43:12 minas-tirith kernel - - - [ 7297.209524] REISERFS (device sda8): found reiserfs format "3.6" with standard journal <0.4> 2021-12-29 12:43:12 minas-tirith kernel - - - [ 7297.209542] reiserfs: using flush barriers <0.4> 2021-12-29 19:26:37 minas-tirith kernel - - - [17069.525728] reiserfs: read-write mode is unsupported. <0.4> 2021-12-29 19:26:37 minas-tirith kernel - - - [17069.525731] reiserfs: load module with allow_unsupported=1 to enable read-write mode. <0.4> 2021-12-29 19:32:22 minas-tirith kernel - - - [ 11.900273] reiserfs: read-write mode is unsupported. <0.4> 2021-12-29 19:32:22 minas-tirith kernel - - - [ 11.900275] reiserfs: load module with allow_unsupported=1 to enable read-write mode. <0.5> 2021-12-29 19:32:22 minas-tirith kernel - - - [ 11.911760] REISERFS (device sda8): found reiserfs format "3.6" with standard journal <0.4> 2021-12-29 19:32:22 minas-tirith kernel - - - [ 11.911776] reiserfs: using flush barriers minas-tirith:~ # There you have, the log clearly says "read-write mode is unsupported", 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. There are no release notes on this decission :-/ - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYcyuUBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVnuQAniU9vLVSOdtNjROXXq0U K3jcBnxUAJwLqMfOZJsGUTMc01rgYyWGJWmrFQ== =FxQ+ -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2021-12-29 at 19:12 +0300, Andrei Borzenkov wrote:
On Wed, Dec 29, 2021 at 6:24 PM Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
Ok, I installed "reiserfs-kmp-default", and now I can mount /home, but only partially (hand copied messages):
mount: /home: WARNING: source write-protected, mount read only.
This means the device is write protected.
mount: /dev/sda8 mounted on /home
I see permissions of device are brw-rw----, I don't understand.
Permissions of device nodes have absolutely nothing to do with the state of the underlying devices. Show full dmesg output.
Since what point, the entire session?
Since bootup, but apply common sense.
is intentional boicot by SUSE/openSUSE :-/
Do you intend to start flamewar?
No, but I'm quite pissed and disturbed :-/ Don't you realize I am hurt?
It is no reason to throw blame about until you have some idea of where to aim.
2021-12-29 12:42:07 minas-tirith 50mounted-tests - - - debug: mounted using GRUB reiserfs filesystem driver 2021-12-29 12:43:12 minas-tirith kernel - - - [ 7297.208721] reiserfs: read-write mode is unsupported.
That seems important.
<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.
ISTR suggesting something along those lines.
There are no release notes on this decission :-/
Yeah, that is poor. -- Per Jessen, Zürich (9.4°C)
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.
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.
There are no release notes on this decission :-/
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/index.html#fate-323394
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.
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.
There are no release notes on this decission :-/
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/index.html#fate-323394
Thanks for finding this, but it is SUSE, not openSUSE. No way I could find this on my own. But it is only about YaST refusing to handle the upgrade, years ago; zypper did not refuse nor even warn. Notice that they *suggest* migrating data partition. Does not say anything about forcing to migrate, and kernel module removal. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
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?" :-)
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. But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful. -- Per Jessen, Zürich (13.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
From: Per Jessen <per@computer.org> Date: Thu, 30 Dec 2021 20:25:13 +0100 Carlos E. R. wrote: . . .
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. But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful. My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code. No new kitten-eating mode would have been implemented. ;-} BTW, this is a good example of why I always do a fresh install in a new partition when upgrading, rather than "zypper dup"; it allows me to fall back on the existing installation if I have issues with the new one, or it takes me longer than I expect to configure and install my software and customizations. As the openSUSE sysadmin and fixit dude for almost 20 years at a company with a minimal hardware budget, I did many system upgrades on older hardware, including a number of Frankenstein models, and had to play it very safe. (Whether or not "zypper dup" actually applies in this case.) -- Bob
On 30/12/2021 21.59, Bob Rogers wrote:
From: Per Jessen <> Date: Thu, 30 Dec 2021 20:25:13 +0100
Carlos E. R. wrote:
. . .
>>> 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. But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful.
My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code. No new kitten-eating mode would have been implemented. ;-}
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
BTW, this is a good example of why I always do a fresh install in a new partition when upgrading, rather than "zypper dup"; it allows me to fall back on the existing installation if I have issues with the new one, or it takes me longer than I expect to configure and install my software and customizations. As the openSUSE sysadmin and fixit dude for almost 20 years at a company with a minimal hardware budget, I did many system upgrades on older hardware, including a number of Frankenstein models, and had to play it very safe. (Whether or not "zypper dup" actually applies in this case.)
I would still hit the same basic problem: the data partitions would be there, inaccessible. Yes, I can revert to the previous install, I have a full backup (both image and rsync files of the root partition, and rsync of the home partition). -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Thu, 30 Dec 2021 22:41:51 +0100 On 30/12/2021 21.59, Bob Rogers wrote:
From: Per Jessen <> Date: Thu, 30 Dec 2021 20:25:13 +0100
Carlos E. R. wrote:
With or without documentation, your laptop might still explode or eat your kittens. But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful.
My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code. No new kitten-eating mode would have been implemented. ;-}
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel. You could try it in the fourth column of /etc/fstab for the /home partition. -- Bob
On 31/12/2021 00.04, Bob Rogers wrote:
From: "Carlos E. R." <> Date: Thu, 30 Dec 2021 22:41:51 +0100
On 30/12/2021 21.59, Bob Rogers wrote: > From: Per Jessen <> > Date: Thu, 30 Dec 2021 20:25:13 +0100 > > Carlos E. R. wrote: > > With or without documentation, your laptop might still explode or eat > your kittens. But I agree, a list of which options are being enabled > by "allow_unsupported=1" would be useful. > > My guess is that the 15.3 kernel module just replaces the rw > functionality with that message by default, and "allow_unsupported=1" > just re-enables the original code. No new kitten-eating mode would have > been implemented. ;-}
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
You could try it in the fourth column of /etc/fstab for the /home partition.
I'm not going to try, I'm reformatting the partition. At the moment, I'm running the rescue disk with 15.2, compressing old files to make space on it. Then I will image that partition, then loop mount it, and restore contents after reformatting as xfs. Trying r/w mode might eat a kitten, so not risking it, at least before creating the image. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Fri, 31 Dec 2021 00:17:43 +0100 On 31/12/2021 00.04, Bob Rogers wrote:
You could try it in the fourth column of /etc/fstab for the /home partition.
I'm not going to try, I'm reformatting the partition. . . . Trying r/w mode might eat a kitten, so not risking it, at least before creating the image. As you wish. I'm sure your kittens are happy that you take no chances with their safety. ;-} -- Bob
* Bob Rogers <rogers-suse@rgrjr.homedns.org> [12-30-21 18:43]:
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Fri, 31 Dec 2021 00:17:43 +0100
On 31/12/2021 00.04, Bob Rogers wrote:
You could try it in the fourth column of /etc/fstab for the /home partition.
I'm not going to try, I'm reformatting the partition.
. . .
Trying r/w mode might eat a kitten, so not risking it, at least before creating the image.
As you wish. I'm sure your kittens are happy that you take no chances with their safety. ;-}
never did like cats, so the mystery will not be solved! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 31/12/2021 00.41, Bob Rogers wrote:
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Fri, 31 Dec 2021 00:17:43 +0100
On 31/12/2021 00.04, Bob Rogers wrote:
> You could try it in the fourth column of /etc/fstab for the /home > partition.
I'm not going to try, I'm reformatting the partition.
. . .
Trying r/w mode might eat a kitten, so not risking it, at least before creating the image.
As you wish. I'm sure your kittens are happy that you take no chances with their safety. ;-}
Yep :-) -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
On 30/12/2021 21.59, Bob Rogers wrote:
My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code.
+1
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader). -- Per Jessen, Zürich (9.2°C)
On 31/12/2021 10.04, Per Jessen wrote:
Carlos E. R. wrote:
On 30/12/2021 21.59, Bob Rogers wrote:
My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code.
+1
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader).
Maybe standard, but I have never done it, so I do not know how exactly to do it. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
On 31/12/2021 10.04, Per Jessen wrote:
Carlos E. R. wrote:
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader).
Maybe standard, but I have never done it, so I do not know how exactly to do it.
I meant "standard" as in well documented, so it is indeed time to read the documentation :-) -- Per Jessen, Zürich (11.2°C)
On 31/12/2021 11.31, Per Jessen wrote:
Carlos E. R. wrote:
On 31/12/2021 10.04, Per Jessen wrote:
Carlos E. R. wrote:
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader).
Maybe standard, but I have never done it, so I do not know how exactly to do it.
I meant "standard" as in well documented, so it is indeed time to read the documentation :-)
A link to that documentation would be nice, because I don't remember having read it or how to find it. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
On 31/12/2021 11.31, Per Jessen wrote:
Carlos E. R. wrote:
On 31/12/2021 10.04, Per Jessen wrote:
Carlos E. R. wrote:
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader).
Maybe standard, but I have never done it, so I do not know how exactly to do it.
I meant "standard" as in well documented, so it is indeed time to read the documentation :-)
A link to that documentation would be nice, because I don't remember having read it or how to find it.
Google is your friend, but maybe it is better to start with "man modprobe". The openSUSE support database will no doubt also be helpful. You can also look at the existing files in /etc/modprobe.d/ to see how it is done. -- Per Jessen, Zürich (13.5°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
On 31/12/2021 12.06, Per Jessen wrote:
Carlos E. R. wrote:
On 31/12/2021 11.31, Per Jessen wrote:
Carlos E. R. wrote:
On 31/12/2021 10.04, Per Jessen wrote:
Carlos E. R. wrote:
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
This is standard stuff though, you don't need any additional documentation for that. Use modinfo to check if it is specific to the filesystem module. The parameter is per-module, so you would just add it to /etc/modprobe.d/ - or you could add it as a kernel argument (in your boot loader).
Maybe standard, but I have never done it, so I do not know how exactly to do it.
I meant "standard" as in well documented, so it is indeed time to read the documentation :-)
A link to that documentation would be nice, because I don't remember having read it or how to find it.
Google is your friend,
When you can think of a proper string to do the search. Often I can't.
but maybe it is better to start with "man modprobe". The openSUSE support database will no doubt also be helpful. You can also look at the existing files in /etc/modprobe.d/ to see how it is done.
Ah, yes, this helps. I think I have figured it out. Thanks. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
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)
Carlos E. R. wrote:
But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful.
And what dangers do I risk.
For one thing, as it turns out, 'allow_unsupported' is a per-module option. Second, you don't risk any "dangers". It is simply a switch to enable some feature or functionality that SUSE does not support. -- Per Jessen, Zürich (14.0°C)
On 31/12/2021 13.16, Carlos E. R. wrote:
On 30/12/2021 20.25, Per Jessen wrote:
Carlos E. R. wrote:
...
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.
Yes, it does work. minas-tirith:~ # cat /etc/modprobe.d/50-reiserfs.conf #CER: reiserfs: load module with allow_unsupported=1 to enable read-write mode options reiserfs allow_unsupported=1 minas-tirith:~ # cd /home minas-tirith:/home # echo "En un lugar de La Mancha" > writing minas-tirith:/home # l wri* -rw-r--r-- 1 root root 25 Dec 31 13:56 writing minas-tirith:/home # Next, reformat as XFS and restore files, unless you want me to do some further testing. Will proceed in a few hours. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2021-12-29 03:24, Carlos E. R. wrote:
Unknown filesystem 'reiserfs'
:-/
<https://bugzilla.opensuse.org/show_bug.cgi?id=1195500> Bug 1195500 - Release notes for 15.3 do not mention that Reiserfs is not supported anymore. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (6)
-
Andrei Borzenkov -
Bob Rogers -
Carlos E. R. -
James Knott -
Patrick Shanahan -
Per Jessen