mount: unknown filesystem type 'nfs' (2.6.24 git) [message #26799] |
Fri, 01 February 2008 05:09 |
John Kelly
Messages: 97 Registered: May 2006 Location: Palmetto State
|
Member |
|
|
NFS client in HN fails with the error:
mount: unknown filesystem type 'nfs'
It works fine with a vanilla 2.6.24 kernel, but 2.6.24-openvz built from git pulled today, fails.
I built both kernels from a custom config, selecting NFSv3 only. The vanilla config and the openvz config are the same, except for the extra options needed for openvz.
Is it a bug?
|
|
|
|
Re: mount: unknown filesystem type 'nfs' (2.6.24 git) [message #26819 is a reply to message #26806] |
Fri, 01 February 2008 13:58 |
John Kelly
Messages: 97 Registered: May 2006 Location: Palmetto State
|
Member |
|
|
2.6.24 works:
Script started on Fri 01 Feb 2008 08:43:27 AM EST
debian:~/temp# lsmod | grep nfs
nfs 106540 1
lockd 53608 2 nfs
sunrpc 144604 8 nfs,lockd
debian:~/temp# modprobe -v nfs
debian:~/temp# lsmod | grep nfs
nfs 106540 1
lockd 53608 2 nfs
sunrpc 144604 8 nfs,lockd
debian:~/temp# tail -n 10 /var/log/messages
Feb 1 08:36:50 debian kernel: agpgart: agp_backend_initialize() failed.
Feb 1 08:36:50 debian kernel: agpgart-serverworks: probe of 0000:00:00.1 failed with error -22
Feb 1 08:36:50 debian kernel: input: Power Button (FF) as /devices/virtual/input/input3
Feb 1 08:36:50 debian kernel: ACPI: Power Button (FF) [PWRF]
Feb 1 08:36:50 debian kernel: EXT3 FS on dm-2, internal journal
Feb 1 08:36:50 debian kernel: loop: module loaded
Feb 1 08:36:50 debian kernel: Adding 524280k swap on /dev/mapper/v0-swap. Priority:-1 extents:1 across:524280k
Feb 1 08:36:50 debian kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Feb 1 08:39:18 debian kernel: RPC: Registered udp transport module.
Feb 1 08:39:18 debian kernel: RPC: Registered tcp transport module.
debian:~/temp# grep nfs /proc/filesystems
nodev nfs
debian:~/temp# exit
exit
Script done on Fri 01 Feb 2008 08:44:38 AM EST
2.6.24-openvz fails:
Script started on Fri 01 Feb 2008 08:50:44 AM EST
debian:~/temp# lsmod | grep nfs
nfs 107596 0
lockd 54792 1 nfs
sunrpc 146300 4 nfs,lockd
debian:~/temp# modprobe -v nfs
debian:~/temp# lsmod | grep nfs
nfs 107596 0
lockd 54792 1 nfs
sunrpc 146300 4 nfs,lockd
debian:~/temp# tail -n 10 /var/log/messages
Feb 1 08:49:12 debian kernel: input: Power Button (FF) as /devices/virtual/input/input3
Feb 1 08:49:12 debian kernel: ACPI: Power Button (FF) [PWRF]
Feb 1 08:49:12 debian kernel: EXT3 FS on dm-2, internal journal
Feb 1 08:49:12 debian kernel: loop: module loaded
Feb 1 08:49:12 debian kernel: Adding 524280k swap on /dev/mapper/v0-swap. Priority:-1 extents:1 across:524280k
Feb 1 08:49:12 debian kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Feb 1 08:49:14 debian kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 1 08:49:14 debian kernel: NET: Registered protocol family 17
Feb 1 08:50:05 debian kernel: RPC: Registered udp transport module.
Feb 1 08:50:05 debian kernel: RPC: Registered tcp transport module.
debian:~/temp# grep nfs /proc/filesystems
debian:~/temp# exit
exit
Script done on Fri 01 Feb 2008 08:51:47 AM EST The difference is that nfs does not appear under filesystems with the openvz kernel. I wonder why? The exact same system is used to boot both kernels.
My kernel config is minimal, I eliminated as much as possible. Maybe some deprecated option is needed by the openvz kernel but not the vanilla?
Or maybe it's an openvz bug?
[Updated on: Fri, 01 February 2008 14:04] Report message to a moderator
|
|
|