[opensuse-factory] reiserfs kernel threads present even after reiserfs kernel module is unloaded
Hello, I'm running 3.16.4-1.g7a8842b-desktop x86_64 from kernel:stable and I observe this on a system without any reiserfs partitions: # ps axu | grep [r]eiser root 16287 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda4] root 16431 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda9] root 25392 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda4] root 25561 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda9] # lsmod | grep reiser # On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in reiserfs kernel threads remaining even after I unloaded the reiserfs kernel module. To verify this, every time I run: #mount /dev/sda4 /mnt -t reiserfs mount: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. #modprobe -r reiserfs another reiserfs kernel thread is added to the aforementioned ones. Should I file a bug report about this? -- Regards, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Fri, 10 Oct 2014 13:23:04 +0300 auxsvr@gmail.com пишет:
Hello,
I'm running 3.16.4-1.g7a8842b-desktop x86_64 from kernel:stable and I observe this on a system without any reiserfs partitions:
# ps axu | grep [r]eiser root 16287 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda4] root 16431 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda9] root 25392 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda4] root 25561 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda9]
# lsmod | grep reiser #
On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in reiserfs kernel threads remaining even after I unloaded the reiserfs kernel module. To verify this, every time I run:
#mount /dev/sda4 /mnt -t reiserfs mount: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so. #modprobe -r reiserfs
another reiserfs kernel thread is added to the aforementioned ones.
Should I file a bug report about this?
What openSUSE version are you using? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, 10/10/2014 auxsvr@gmail.com :
Hello,
I'm running 3.16.4-1.g7a8842b-desktop x86_64 from kernel:stable and I observe this on a system without any reiserfs partitions:
# ps axu | grep [r]eiser root 16287 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda4] root 16431 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda9] root 25392 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda4] root 25561 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda9]
# lsmod | grep reiser #
On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in reiserfs kernel threads remaining even after I unloaded the reiserfs kernel module. To verify this, every time I run:
#mount /dev/sda4 /mnt -t reiserfs mount: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so. #modprobe -r reiserfs
another reiserfs kernel thread is added to the aforementioned ones.
I confirm this on tumbleweed x86_64. The kernel is 3.16.3-49.gd2bbe7f-desktop. Here is what I did as a test: dd </dev/zero >plop bs=1M count=1 for i in $(seq 100); do mount -t reiserfs plop /mnt/ -o loop; done And now I have a hundred reiserfs kernel threads, even after unloading the module.
Should I file a bug report about this?
Definitely. -- Benoît -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/2014, 08:29 PM, Benoît Monin wrote:
Hi,
10/10/2014 auxsvr@gmail.com :
Hello,
I'm running 3.16.4-1.g7a8842b-desktop x86_64 from kernel:stable and I observe this on a system without any reiserfs partitions:
# ps axu | grep [r]eiser root 16287 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda4] root 16431 0.0 0.0 0 0 ? S< Oct09 0:00 [reiserfs/sda9] root 25392 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda4] root 25561 0.0 0.0 0 0 ? S< Oct08 0:00 [reiserfs/sda9]
# lsmod | grep reiser #
On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in reiserfs kernel threads remaining even after I unloaded the reiserfs kernel module. To verify this, every time I run:
#mount /dev/sda4 /mnt -t reiserfs mount: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so. #modprobe -r reiserfs
another reiserfs kernel thread is added to the aforementioned ones.
I confirm this on tumbleweed x86_64. The kernel is 3.16.3-49.gd2bbe7f-desktop. Here is what I did as a test:
dd </dev/zero >plop bs=1M count=1 for i in $(seq 100); do mount -t reiserfs plop /mnt/ -o loop; done
And now I have a hundred reiserfs kernel threads, even after unloading the module.
Should I file a bug report about this?
Definitely.
This is now bug 909736 which has perhaps a fix already :). -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2014-10-10 at 13:23 +0300, auxsvr@gmail.com wrote:
On 8 and 9/10, the system log indicates that os-prober attempted to mount sda4 and sda9 using every possible filesystem kernel module, but sda4 is an extended partition and sda9 is an unformatted one, which probably resulted in
That rings a bell. I reported that issue long ago. Let me see... found it: Date: Thu, 6 Mar 2014 12:48:14 +0000 Subject: [Bug 867118] New: os-prober tries to mount all extended partitions, causing awful kernel messages https://bugzilla.novell.com/show_bug.cgi?id=867118 So, not an unknown problem. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSLTG8ACgkQtTMYHG2NR9VmFQCgiKdzFjUP8s/oxU6k0s4RaN9v sxkAoJf6AThG7mRHj+nqW4ivP7nza1r5 =bJa4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
auxsvr＠gmail.com -
Benoît Monin -
Carlos E. R. -
Jiri Slaby