Skip to contentSkip to conversation

NFS on little-endian platform - Microblaze

DISCUSSION Michal Simek 3 participants 7 messages Feb 16, 2011 – Feb 17, 2011 3 messages not in the archive

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

Hi All,

I am trying to understand one problem which we have found.
The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below)
Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101) ~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
~ # cat /proc/cpuinfo
CPU-Family:     MicroBlaze
FPGA-Arch:      spartan6
CPU-Ver:        8.00.a, little endian
CPU-MHz:        50.00
BogoMips:       24.06
HW:
 Shift:         yes
 MSR:           yes
 PCMP:          yes
 DIV:           yes
 MMU:           3
 MUL:           v2
 FPU:           no
 Exc:           op0x0 unal ill iopb dopb zero
Icache:         16kB    line length:    32B
Dcache:         16kB    line length:    16B
                write-through
HW-Debug:       yes
PVR-USR1:       00
PVR-USR2:       00000000
Page size:      4096

~ #

Signature · 4 lines
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 82 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found.
The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below)
Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
~ # cat /proc/cpuinfo
CPU-Family:     MicroBlaze
FPGA-Arch:      spartan6
CPU-Ver:        8.00.a, little endian
CPU-MHz:        50.00
BogoMips:       24.06
HW:
 Shift:         yes
 MSR:           yes
 PCMP:          yes
 DIV:           yes
 MMU:           3
 MUL:           v2
 FPU:           no
 Exc:           op0x0 unal ill iopb dopb zero
Icache:         16kB    line length:    32B
Dcache:         16kB    line length:    16B
                write-through
HW-Debug:       yes
PVR-USR1:       00
PVR-USR2:       00000000
Page size:      4096

~ #

Signature · 8 lines
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
Quoted 68 lines · Michal Simek

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 59 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found. The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below) Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps

Where is rpc.statd? Without it, the above behaviour is 100% expected.

Trond

Signature · 6 lines
Trond Myklebust
Linux NFS client maintainer

NetApp
[email protected]
www.netapp.com

A message that is not in the archive (sent off-list or not yet received): 1297862575.6596.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#5 lore raw
Quoted 67 lines · Trond Myklebust
Quoted 65 lines · Michal Simek

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 56 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found.
The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below)
Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
Quoted 1 line

Where is rpc.statd? Without it, the above behaviour is 100% expected.

I see on BE that lockd is used but it is enabled on little endian too but hasn't started.

Enabled options:
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

On Be lockd is up.

   69 root       0:00 /bin/flatfsd
   71 root       0:00 [lockd]
   73 root       0:00 ps

I have to look why.
How is it started?

Michal

Signature · 8 lines
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#6 lore raw
Quoted 84 lines · Michal Simek
Quoted 70 lines · Trond Myklebust
Quoted 68 lines · Michal Simek

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 59 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found. The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below) Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
Quoted 1 line

Where is rpc.statd? Without it, the above behaviour is 100% expected.

I see on BE that lockd is used but it is enabled on little endian too but hasn't started.

Enabled options:
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

Quoted 7 lines

On Be lockd is up.

    69 root       0:00 /bin/flatfsd
    71 root       0:00 [lockd]
    73 root       0:00 ps

I have to look why.
How is it started?

Either rpc.bind or rpc.portmap and then rpc.statd need to be started manually (in that order) before you may mount the NFS partition without '-onolock'. The lockd daemon itself will be started by the kernel whenever there is a need for it.

Please check your 'init' boot scripts to find out why they are not being started as expected.

Signature · 6 lines
Trond Myklebust
Linux NFS client maintainer

NetApp
[email protected]
www.netapp.com

A message that is not in the archive (sent off-list or not yet received): 1297865074.6596.10.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#8 lore raw
Quoted 85 lines · Trond Myklebust
Quoted 84 lines · Michal Simek
Quoted 66 lines · Trond Myklebust
Quoted 65 lines · Michal Simek

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 56 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found.
The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below)
Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
Quoted 1 line

Where is rpc.statd? Without it, the above behaviour is 100% expected.

I see on BE that lockd is used but it is enabled on little endian too but hasn't started.

Enabled options:
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

On Be lockd is up.

    69 root       0:00 /bin/flatfsd
    71 root       0:00 [lockd]
    73 root       0:00 ps
Quoted 7 lines
Quoted 2 lines

I have to look why.
How is it started?

Either rpc.bind or rpc.portmap and then rpc.statd need to be started manually (in that order) before you may mount the NFS partition without '-onolock'. The lockd daemon itself will be started by the kernel whenever there is a need for it.

On big-endian system is not any rpc* binary either that's why I think this is not a problem. Only portmap is started on both systems. Nothing more. If you want I can send you cpio archive.

Quoted 3 lines

Please check your 'init' boot scripts to find out why they are not being started as expected.

ok.

Michal

Signature · 8 lines
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#9 lore raw
In reply to a message not in the archive
Quoted 88 lines · Trond Myklebust
Quoted 79 lines · Michal Simek
Quoted 66 lines · Trond Myklebust
Quoted 65 lines · Michal Simek

Hi again,

I forget to cc linux-nfs mailing list.

Michal

P.S.: Tested on kernels 2.6.38-rc4, 2.6.37 and 2.6.36

Quoted 56 lines · Michal Simek

Hi All,

I am trying to understand one problem which we have found.
The problem is that I can't on Microblaze little-endian platform mount nfs without -o nolock options. (Log below)
Selecting tcp or udp has no effect.
I am using emaclite driver and there is no problem on big endian microblaze.

ping, telnet, http, ftp, iperf, netperf work well.

That's why I have a question if there is any endian specific option for NFS?

Thanks,
Michal

~ # mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt
svc: failed to register lockdv1 RPC service (errno 13).
lockd_up: makesock failed, error=-13
svc: failed to register lockdv1 RPC service (errno 13).
~ # mount -t nfs -o nolock 192.168.0.101:/tftpboot/nfs /mnt
~ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /var type ramfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /etc/config type ramfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
192.168.0.101:/tftpboot/nfs on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.101)

~ #
~ # ps
PID USER TIME COMMAND

    1 root       0:02 init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    4 root       0:00 [kworker/0:0]
    5 root       0:00 [kworker/u:0]
    6 root       0:00 [khelper]
    7 root       0:00 [sync_supers]
    8 root       0:00 [bdi-default]
    9 root       0:00 [kblockd]
   10 root       0:00 [rpciod]
   11 root       0:00 [kworker/0:1]
   12 root       0:00 [kswapd0]
   13 root       0:00 [fsnotify_mark]
   14 root       0:00 [aio]
   15 root       0:00 [nfsiod]
   16 root       0:00 [kworker/u:1]
   58 root       0:00 udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
   62 1          0:00 /bin/portmap
   64 root       0:00 /bin/inetd /etc/inetd.conf
   65 root       0:01 -sh
   66 root       0:00 /bin/syslogd -n
   67 root       0:00 /bin/flatfsd
   68 root       0:00 [kworker/0:2]
   91 root       0:00 ps
Quoted 1 line

Where is rpc.statd? Without it, the above behaviour is 100% expected.

I see on BE that lockd is used but it is enabled on little endian too but hasn't started.

Enabled options:
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

Quoted 7 lines

On Be lockd is up.

    69 root       0:00 /bin/flatfsd
    71 root       0:00 [lockd]
    73 root       0:00 ps

I have to look why.
How is it started?

Quoted 8 lines

Either rpc.bind or rpc.portmap and then rpc.statd need to be started manually (in that order) before you may mount the NFS partition without '-onolock'. The lockd daemon itself will be started by the kernel whenever there is a need for it.

Please check your 'init' boot scripts to find out why they are not being started as expected.

It seems to me that the problem is with sunrpc in connection to endian. I am looking for any package which can test sunrpc on embedded systems. Can you recommend me any package?

I have found RPC tests in LTP but it is designed for desktops not embedded.

Thanks,
Michal

Signature · 8 lines
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html