| 1 |
Hi all.this is my first message in mail list, so correct me if I 'm wrong. |
| 2 |
I have a raspberry pi with kernel compiled from |
| 3 |
(sys-kernel/raspberrypi-source 3.6.11_r20130711,running nfsv4 server.To |
| 4 |
simplify problem, only a simple directory exported. |
| 5 |
|
| 6 |
Senge-Raspi ~ # cat /etc/exports |
| 7 |
# /etc/exports: NFS file systems being exported. See exports(5). |
| 8 |
/export *(fsid=0,rw,no_subtree_check,no_root_squash) |
| 9 |
Senge-Raspi ~ # ls -l /export/ |
| 10 |
total 4 |
| 11 |
-rw-r--r-- 1 root root 4 Nov 18 12:48 test |
| 12 |
Senge-Raspi ~ # cat /export/test |
| 13 |
foo |
| 14 |
|
| 15 |
And on my laptop, as nfs client. |
| 16 |
|
| 17 |
senge@Senge-Laptop ~ $ cat /etc/fstab |
| 18 |
# <fs> <mountpoint> <type> <opts> |
| 19 |
<dump/pass> |
| 20 |
|
| 21 |
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. |
| 22 |
/dev/sda1 /boot ext4 |
| 23 |
noauto,noatime 1 2 |
| 24 |
/dev/sda3 / ext4 |
| 25 |
noatime 0 1 |
| 26 |
/dev/sda2 none swap |
| 27 |
sw 0 0 |
| 28 |
/dev/sda4 /mnt/windows ntfs |
| 29 |
noauto 0 0 |
| 30 |
59.78.22.20:/ /raspi nfs4 |
| 31 |
rw,_netdev,auto,rsize=32768,wsize=32768 0 0 |
| 32 |
senge@Senge-Laptop ~ $ sudo rc-config restart nfsmount |
| 33 |
Restarting init script |
| 34 |
* Starting rpcbind |
| 35 |
... |
| 36 |
[ ok ] |
| 37 |
* Starting NFS statd |
| 38 |
... |
| 39 |
[ ok ] |
| 40 |
* Setting up RPC pipefs |
| 41 |
... |
| 42 |
[ ok ] |
| 43 |
* Starting idmapd |
| 44 |
... |
| 45 |
[ ok ] |
| 46 |
* Starting NFS sm-notify |
| 47 |
... |
| 48 |
[ ok ] |
| 49 |
* Mounting NFS filesystems ... |
| 50 |
|
| 51 |
It hangs here. and in kernel message |
| 52 |
[19888.585247] RPC: Registered named UNIX socket transport module. |
| 53 |
[19888.585251] RPC: Registered udp transport module. |
| 54 |
[19888.585252] RPC: Registered tcp transport module. |
| 55 |
[19888.585253] RPC: Registered tcp NFSv4.1 backchannel transport module. |
| 56 |
[19889.214956] NFS: Registering the id_resolver key type |
| 57 |
[19889.214973] Key type id_resolver registered |
| 58 |
[19889.214974] Key type id_legacy registered |
| 59 |
[20054.134247] NFS: nfs4_discover_server_trunking unhandled error -512. |
| 60 |
Exiting with error EIO |
| 61 |
|
| 62 |
sometimes mount succeed, and directory can be accessed. but reading files |
| 63 |
return error:(without 'dmesg' changed) |
| 64 |
senge@Senge-Laptop ~ $ sudo rc-config restart nfsmount |
| 65 |
Restarting init script |
| 66 |
* Starting NFS sm-notify |
| 67 |
... |
| 68 |
[ ok ] |
| 69 |
* Mounting NFS filesystems |
| 70 |
... |
| 71 |
[ ok ] |
| 72 |
senge@Senge-Laptop ~ $ cat /raspi/test |
| 73 |
cat: /raspi/test: Input/Output error |
| 74 |
|
| 75 |
But I actually have nfs support on server: |
| 76 |
Senge-Raspi ~ # zcat /proc/config.gz | grep -i nfs |
| 77 |
# CONFIG_NFS_FS is not set |
| 78 |
CONFIG_NFSD=y |
| 79 |
CONFIG_NFSD_V2_ACL=y |
| 80 |
CONFIG_NFSD_V3=y |
| 81 |
CONFIG_NFSD_V3_ACL=y |
| 82 |
CONFIG_NFSD_V4=y |
| 83 |
# CONFIG_NFSD_FAULT_INJECTION is not set |
| 84 |
CONFIG_NFS_ACL_SUPPORT=y |
| 85 |
CONFIG_NFS_COMMON=y |
| 86 |
|
| 87 |
However, official pre-compiled kernel(sys-kernel/raspberrypi-image |
| 88 |
3.6.11-p20130730) worked fine, |
| 89 |
Senge-Raspi ~ # zcat /proc/config.gz | grep -i nfs |
| 90 |
CONFIG_NFS_FS=y |
| 91 |
CONFIG_NFS_V2=y |
| 92 |
CONFIG_NFS_V3=y |
| 93 |
CONFIG_NFS_V3_ACL=y |
| 94 |
CONFIG_NFS_V4=y |
| 95 |
# CONFIG_NFS_SWAP is not set |
| 96 |
# CONFIG_NFS_V4_1 is not set |
| 97 |
CONFIG_ROOT_NFS=y |
| 98 |
CONFIG_NFS_FSCACHE=y |
| 99 |
# CONFIG_NFS_USE_LEGACY_DNS is not set |
| 100 |
CONFIG_NFS_USE_KERNEL_DNS=y |
| 101 |
CONFIG_NFSD=m |
| 102 |
CONFIG_NFSD_V2_ACL=y |
| 103 |
CONFIG_NFSD_V3=y |
| 104 |
CONFIG_NFSD_V3_ACL=y |
| 105 |
CONFIG_NFSD_V4=y |
| 106 |
# CONFIG_NFSD_FAULT_INJECTION is not set |
| 107 |
CONFIG_NFS_ACL_SUPPORT=y |
| 108 |
CONFIG_NFS_COMMON=y |
| 109 |
|
| 110 |
|
| 111 |
I have googled a lot, return few result...any idea appreciated.(sorry for |
| 112 |
poor English) |
Archives