1 |
Thanks for reply! However, CONFIG_NFS_FS is a client config, and probably |
2 |
not related to my server problem. |
3 |
|
4 |
Symbol: NFS_FS |
5 |
[=n] |
6 |
|
7 |
Type : |
8 |
tristate |
9 |
|
10 |
Prompt: NFS client |
11 |
support |
12 |
|
13 |
Defined at |
14 |
fs/nfs/Kconfig:1 |
15 |
|
16 |
Depends on: NETWORK_FILESYSTEMS [=y] && INET [=y] && FILE_LOCKING |
17 |
[=y] |
18 |
|
19 |
Location: |
20 |
|
21 |
-> File |
22 |
systems |
23 |
|
24 |
-> Network File Systems (NETWORK_FILESYSTEMS |
25 |
[=y]) |
26 |
|
27 |
Selects: LOCKD [=y] && SUNRPC [=y] && NFS_ACL_SUPPORT |
28 |
[=y] |
29 |
|
30 |
|
31 |
by the way, here is my laptop config: |
32 |
senge@Senge-Laptop ~ $ zcat /proc/config.gz | grep -i nfs |
33 |
CONFIG_NFS_FS=m |
34 |
# CONFIG_NFS_V2 is not set |
35 |
# CONFIG_NFS_V3 is not set |
36 |
CONFIG_NFS_V4=m |
37 |
# CONFIG_NFS_SWAP is not set |
38 |
# CONFIG_NFS_V4_1 is not set |
39 |
# CONFIG_NFS_USE_LEGACY_DNS is not set |
40 |
CONFIG_NFS_USE_KERNEL_DNS=y |
41 |
# CONFIG_NFSD is not set |
42 |
CONFIG_NFS_COMMON=y |
43 |
|
44 |
more info: |
45 |
Senge-Laptop ~ # rpcinfo -p 59.78.22.20 |
46 |
program vers proto port service |
47 |
100000 4 tcp 111 portmapper |
48 |
100000 3 tcp 111 portmapper |
49 |
100000 2 tcp 111 portmapper |
50 |
100000 4 udp 111 portmapper |
51 |
100000 3 udp 111 portmapper |
52 |
100000 2 udp 111 portmapper |
53 |
100024 1 udp 59999 status |
54 |
100024 1 tcp 34251 status |
55 |
100003 2 tcp 2049 nfs |
56 |
100003 3 tcp 2049 nfs |
57 |
100003 4 tcp 2049 nfs |
58 |
100227 2 tcp 2049 nfs_acl |
59 |
100227 3 tcp 2049 nfs_acl |
60 |
100003 2 udp 2049 nfs |
61 |
100003 3 udp 2049 nfs |
62 |
100003 4 udp 2049 nfs |
63 |
100227 2 udp 2049 nfs_acl |
64 |
100227 3 udp 2049 nfs_acl |
65 |
100021 1 udp 37157 nlockmgr |
66 |
100021 3 udp 37157 nlockmgr |
67 |
100021 4 udp 37157 nlockmgr |
68 |
100021 1 tcp 45755 nlockmgr |
69 |
100021 3 tcp 45755 nlockmgr |
70 |
100021 4 tcp 45755 nlockmgr |
71 |
|
72 |
it seem that nfs service is on, and client can connect the service. |
73 |
2013/11/18 edwardunix@××××.com <edwardunix@××××.com> |
74 |
|
75 |
> On 11/17/2013 9:17 PM, 钱泽森 wrote: |
76 |
> |
77 |
>> [ ok ] |
78 |
>> senge@Senge-Laptop ~ $ cat /raspi/test |
79 |
>> cat: /raspi/test: Input/Output error |
80 |
>> |
81 |
>> But I actually have nfs support on server: |
82 |
>> Senge-Raspi ~ # zcat /proc/config.gz | grep -i nfs |
83 |
>> # CONFIG_NFS_FS is not set |
84 |
>> |
85 |
> |
86 |
> CONFIG_NFS_FS is set to y in the kernel shown below. |
87 |
> Probably this setting no being set is what is causing the problem. |
88 |
> |
89 |
> |
90 |
> CONFIG_NFSD=y |
91 |
>> CONFIG_NFSD_V2_ACL=y |
92 |
>> CONFIG_NFSD_V3=y |
93 |
>> CONFIG_NFSD_V3_ACL=y |
94 |
>> CONFIG_NFSD_V4=y |
95 |
>> # CONFIG_NFSD_FAULT_INJECTION is not set |
96 |
>> CONFIG_NFS_ACL_SUPPORT=y |
97 |
>> CONFIG_NFS_COMMON=y |
98 |
>> |
99 |
>> However, official pre-compiled kernel(sys-kernel/raspberrypi-image |
100 |
>> 3.6.11-p20130730) worked fine, |
101 |
>> Senge-Raspi ~ # zcat /proc/config.gz | grep -i nfs |
102 |
>> CONFIG_NFS_FS=y |
103 |
>> CONFIG_NFS_V2=y |
104 |
>> CONFIG_NFS_V3=y |
105 |
>> CONFIG_NFS_V3_ACL=y |
106 |
>> CONFIG_NFS_V4=y |
107 |
>> # CONFIG_NFS_SWAP is not set |
108 |
>> # CONFIG_NFS_V4_1 is not set |
109 |
>> CONFIG_ROOT_NFS=y |
110 |
>> CONFIG_NFS_FSCACHE=y |
111 |
>> # CONFIG_NFS_USE_LEGACY_DNS is not set |
112 |
>> CONFIG_NFS_USE_KERNEL_DNS=y |
113 |
>> CONFIG_NFSD=m |
114 |
>> CONFIG_NFSD_V2_ACL=y |
115 |
>> CONFIG_NFSD_V3=y |
116 |
>> CONFIG_NFSD_V3_ACL=y |
117 |
>> CONFIG_NFSD_V4=y |
118 |
>> # CONFIG_NFSD_FAULT_INJECTION is not set |
119 |
>> CONFIG_NFS_ACL_SUPPORT=y |
120 |
>> CONFIG_NFS_COMMON=y |
121 |
>> |
122 |
>> |
123 |
>> I have googled a lot, return few result...any idea appreciated.(sorry for |
124 |
>> poor English) |
125 |
>> |
126 |
> |
127 |
> |
128 |
> |