[PVE-User] unable to load ext4 module, and after, all modules can't be loaded

Germain Maurice germain.maurice at linkfluence.net
Thu Apr 7 19:06:48 CEST 2011


Hi everybody,

I have a 5 node cluster with PVE and i got a problem with ext4 support 
(the visible part of the iceberg).
I installed my cluster, a few month ago, with 1.5 iso. After the 1.7 
release, i upgraded the nodes. They
seemed to work fine until now.

The ext4 module was not loaded as you can see in the following lsmod.

node4:~# lsmod
Module                  Size  Used by
ipmi_si                30976  1
mpt2sas                87197  1
mptctl                 20815  1
ipmi_devintf            6603  2
ipmi_msghandler        26634  2 ipmi_si,ipmi_devintf
dell_rbu                4663  0
tun                    12299  8
aoe                    42304  2
kvm_intel              38066  16
kvm                   213640  1 kvm_intel
vzethdev                7189  0
vznetdev               17967  0
simfs                   2991  0
vzrst                 108343  0
vzcpt                  95250  0
vzdquota               34774  0 [permanent]
vzmon                  16221  4 vzethdev,vznetdev,vzrst,vzcpt
vzdev                   1824  4 vzethdev,vznetdev,vzdquota,vzmon
xt_tcpudp               2319  0
xt_length               1164  0
xt_hl                   1313  0
xt_tcpmss               1401  0
xt_TCPMSS               2935  0
iptable_mangle          2881  0
iptable_filter          2322  1
xt_multiport            2267  1
xt_limit                1782  0
xt_dscp                 1805  0
ipt_REJECT              1953  0
ip_tables              14107  2 iptable_mangle,iptable_filter
x_tables               13117  10 
xt_tcpudp,xt_length,xt_hl,xt_tcpmss,xt_TCPMSS,xt_multiport,xt_limit,xt_dscp,ipt_REJECT,ip_tables
ib_iser                24210  0
rdma_cm                20486  1 ib_iser
ib_cm                  26192  1 rdma_cm
iw_cm                   6275  1 rdma_cm
ib_sa                  16199  2 rdma_cm,ib_cm
ib_mad                 29825  2 ib_cm,ib_sa
ib_core                40679  6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
ib_addr                 4389  1 rdma_cm
iscsi_tcp               8017  0
libiscsi_tcp           10898  1 iscsi_tcp
libiscsi               29206  3 ib_iser,iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi    24844  4 ib_iser,iscsi_tcp,libiscsi
bridge                 40294  0
stp                     1440  1 bridge
bonding                73895  0
snd_pcm                60519  0
snd_timer              15550  1 snd_pcm
snd                    46398  2 snd_pcm,snd_timer
soundcore               4598  1 snd
snd_page_alloc          6137  1 snd_pcm
dcdbas                  5000  0
evdev                   7368  0
pcspkr                  1699  0
psmouse                49681  0
serio_raw               3768  0
power_meter             8206  0
button                  4682  0
processor              29759  0
ext3                  105398  3
jbd                    36509  1 ext3
mbcache                 5050  1 ext3
dm_mirror              10827  0
dm_region_hash          6584  1 dm_mirror
dm_log                  7381  2 dm_mirror,dm_region_hash
dm_snapshot            18289  0
ata_piix               21028  0
ata_generic             3047  0
ehci_hcd               30559  0
libata                132896  2 ata_piix,ata_generic
uhci_hcd               18393  0
usbcore               121650  3 ehci_hcd,uhci_hcd
nls_base                6377  1 usbcore
igb                   118261  0
dca                     3761  1 igb
mptsas                 28948  2
mptscsih               16328  1 mptsas
mptbase                48206  3 mptctl,mptsas,mptscsih
scsi_transport_sas     19673  2 mpt2sas,mptsas
bnx2                  172069  0
thermal                11754  0
fan                     3362  0
thermal_sys            11942  3 processor,thermal,fan



So i try to load it... i got errors.

node4:~# modprobe ext4
WARNING: Could not open 'kernel/lib/crc16.ko': No such file or directory
WARNING: Could not open 'kernel/fs/jbd2/jbd2.ko': No such file or directory
WARNING: Could not open 'kernel/fs/mbcache.ko': No such file or directory
FATAL: Could not open 'kernel/fs/ext4/ext4.ko': No such file or directory

I checked i effectively don't have the missing modules.

Actually, i get them, but in /lib/modules/2.6.32-4pve/

node4:~# ls /lib/modules/2.6.32-4-pve/kernel/lib/crc16.ko
/lib/modules/2.6.32-4-pve/kernel/lib/crc16.ko
node4:~# ls /lib/modules/2.6.32-4-pve/kernel/fs/jbd2/jbd2.ko
/lib/modules/2.6.32-4-pve/kernel/fs/jbd2/jbd2.ko
node4:~# ls /lib/modules/2.6.32-4-pve/kernel/fs/mbcache.ko
/lib/modules/2.6.32-4-pve/kernel/fs/mbcache.ko
node4:~# ls /lib/modules/2.6.32-4-pve/kernel/fs/ext4/ext4.ko
/lib/modules/2.6.32-4-pve/kernel/fs/ext4/ext4.ko
node4:~#

If i make an insmod for each module, it works.

Actually, if i restart the node, the host is unable to modprobe kvm, 
bonding and others.
Has man modprobe said, modprobe will load the modules that reside under 
/lib/modules/`uname -r`
so why it does not do it ?

The problem can be resolved, for a proper restart of the host, by 
launching "depmod".
Before depmod i had :
node4:~# head /lib/modules/2.6.32-4-pve/modules.dep
kernel/arch/x86/kernel/cpu/mcheck/mce-inject.ko:
kernel/arch/x86/kernel/cpu/cpufreq/powernow-k8.ko: 
kernel/drivers/acpi/processor.ko kernel/drivers/thermal/thermal_sys.ko
kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko: 
kernel/drivers/acpi/processor.ko kernel/drivers/thermal/thermal_sys.ko
kernel/arch/x86/kernel/cpu/cpufreq/speedstep-centrino.ko:
kernel/arch/x86/kernel/msr.ko:
kernel/arch/x86/kernel/cpuid.ko:
kernel/arch/x86/kernel/microcode.ko:
kernel/arch/x86/crypto/aes-x86_64.ko: kernel/crypto/aes_generic.ko
kernel/arch/x86/crypto/twofish-x86_64.ko: kernel/crypto/twofish_common.ko
kernel/arch/x86/crypto/salsa20-x86_64.ko:


After, i have the full paths for each module and the reboot works properly.

node1# head /lib/modules/2.6.32-4-pve/modules.dep
/lib/modules/2.6.32-4-pve/extra/scst/scst_user.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_processor.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/iscsi-scst.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko 
/lib/modules/2.6.32-4-pve/kernel/lib/libcrc32c.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_raid.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_changer.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_tape.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_vdisk.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_modisk.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_cdrom.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko
/lib/modules/2.6.32-4-pve/extra/scst/scst_disk.ko: 
/lib/modules/2.6.32-4-pve/extra/scst/scst.ko


Here is the pveversion :
node4:~# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.18: 1.7-10
pve-kernel-2.6.32-4-pve: 2.6.32-30
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.18-4-pve: 2.6.18-10
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-10


How to ensure that modprobe has the right behavior ?

It's a big email, so, thank you for having reading it.
Any idea is really welcome.
Regards,
Germain

-- 
Germain Maurice
Administrateur Système/Réseau
Tel : +33.(0)1.42.43.54.33

http://www.linkfluence.net




More information about the pve-user mailing list