| Miklos Szeredi | 307242f | 2004-01-26 11:28:44 +0000 | [diff] [blame] | 1 | NFS exporting is supported on kernels versions >= 2.6.0. For 2.4.X |
| 2 | kernels the exporting infrastructure is not refined enough, so don't |
| 3 | expect this to work. |
| Miklos Szeredi | e815c03 | 2004-01-19 18:20:49 +0000 | [diff] [blame] | 4 | |
| Miklos Szeredi | 217042f | 2005-09-26 09:07:43 +0000 | [diff] [blame] | 5 | Also FUSE module in official kernels (>= 2.6.14) don't support NFS |
| 6 | exporting. In this case if you need NFS exporting capability, use the |
| 7 | '--enable-kernel-module' configure option to compile the module from |
| 8 | this package. And make sure, that the FUSE is not compiled into the |
| 9 | kernel (CONFIG_FUSE_FS must be 'm' or 'n'). |
| 10 | |
| Miklos Szeredi | e815c03 | 2004-01-19 18:20:49 +0000 | [diff] [blame] | 11 | You need to add an fsid=NNN option to /etc/exports to make exporting a |
| 12 | FUSE directory work. |
| 13 | |
| 14 | You may get ESTALE (Stale NFS file handle) errors with this. This is |
| 15 | because the current FUSE kernel API and the userspace library cannot |
| Miklos Szeredi | 307242f | 2004-01-26 11:28:44 +0000 | [diff] [blame] | 16 | handle a situation where the kernel forgets about an inode which is |
| Miklos Szeredi | e815c03 | 2004-01-19 18:20:49 +0000 | [diff] [blame] | 17 | still referenced by the remote NFS client. This problem will be |
| 18 | addressed in a later version. |
| Miklos Szeredi | 217042f | 2005-09-26 09:07:43 +0000 | [diff] [blame] | 19 | |
| 20 | In the future it planned that NFS exporting will be done solely in |
| 21 | userspace. |