Well, didn't notice it earlier, but modinfo is showing 2.6.31-15 which
it should not. Just clear out the the system is indeed using the -16
kenrel, uname -a output follows:
Linux archangel 2.6.31-16-server #53-Ubuntu SMP Tue Dec 8 05:08:02 UTC
2009 x86_64 GNU/Linux
And the drbd module for 2.6.31-16 does exist. Because a locate drbd.ko
returns the following reuslt:
> I believe there might be two versions of the module: the in-kernel and a
> DKMS external one. When booted into the -16 kernel, can you do a
> "modinfo drbd" and attach the output. While being on it, also do a "dkms
> status" and also attach that output to the bug report.
>
Hello,
so I started with the -16 kernel and as requested here are the outputs
from modinfo and dkms
#modinfo drbd:
On Mon, 2009-12-14 at 13:21 +0000, Stefan Bader wrote:modinfo drbd 2.6.31- 16-server/ updates/ dkms/drbd. ko 71AA1BA8 sendpage: bool helper: string
filename: /lib/modules/
alias: block-major-147-*
license: GPL
version: 8.3.3
description: drbd - Distributed Replicated Block Device v8.3.3
author: Philipp Reisner <email address hidden>, Lars Ellenberg
<email address hidden>
srcversion: 8F005DC598E07E7
depends:
vermagic: 2.6.31-15-server SMP mod_unload modversions
parm: minor_count:Maximum number of drbd devices (1-255)
(uint)
parm: disable_
parm: allow_oos:DONT USE! (bool)
parm: cn_idx:uint
parm: proc_details:int
parm: enable_faults:int
parm: fault_rate:int
parm: fault_count:int
parm: fault_devs:int
parm: usermode_
#dkms status:
drbd8, 8.3.3, 2.6.31-15-server, x86_64: installed
drbd8, 8.3.3, 2.6.31-16-generic, x86_64: installed
drbd8, 8.3.3, 2.6.31-16-server, x86_64: installed
drbd8, 8.3.3, 2.6.31-14-server, x86_64: installed
drbd8, 8.3.3, 2.6.31-15-generic, x86_64: installed
Well, didn't notice it earlier, but modinfo is showing 2.6.31-15 which
it should not. Just clear out the the system is indeed using the -16
kenrel, uname -a output follows:
Linux archangel 2.6.31-16-server #53-Ubuntu SMP Tue Dec 8 05:08:02 UTC
2009 x86_64 GNU/Linux
And the drbd module for 2.6.31-16 does exist. Because a locate drbd.ko
returns the following reuslt:
#locate drbd.ko
/lib/modules/ 2.6.31- 11-server/ kernel/ ubuntu/ drbd/drbd. ko 2.6.31- 14-server/ kernel/ ubuntu/ drbd/drbd. ko 2.6.31- 14-server/ updates/ dkms/drbd. ko 2.6.31- 15-generic/ updates/ dkms/drbd. ko 2.6.31- 15-server/ kernel/ ubuntu/ drbd/drbd. ko 2.6.31- 15-server/ updates/ dkms/drbd. ko 2.6.31- 16-generic/ updates/ dkms/drbd. ko 2.6.31- 16-server/ kernel/ ubuntu/ drbd/drbd. ko 2.6.31- 16-server/ updates/ dkms/drbd. ko dkms/drbd8/ 8.3.3/2. 6.31-14- server/ x86_64/ module/ drbd.ko dkms/drbd8/ 8.3.3/2. 6.31-15- generic/ x86_64/ module/ drbd.ko dkms/drbd8/ 8.3.3/2. 6.31-15- server/ x86_64/ module/ drbd.ko dkms/drbd8/ 8.3.3/2. 6.31-16- generic/ x86_64/ module/ drbd.ko dkms/drbd8/ 8.3.3/2. 6.31-16- server/ x86_64/ module/ drbd.ko
/lib/modules/
/lib/modules/
/lib/modules/
/lib/modules/
/lib/modules/
/lib/modules/
/lib/modules/
/lib/modules/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
> I believe there might be two versions of the module: the in-kernel and a
> DKMS external one. When booted into the -16 kernel, can you do a
> "modinfo drbd" and attach the output. While being on it, also do a "dkms
> status" and also attach that output to the bug report.
>