| 1 |
> I'm trying to be a good gentoo netizen by nfs-sharing /usr/portage between |
| 2 |
> my three local gentoo machines, and failing :( |
| 3 |
> |
| 4 |
> After weeks of fiddling, I discovered today that my problems come from |
| 5 |
> using a 32-bit machine to serve my two 64-bit NFS clients(!) |
| 6 |
> |
| 7 |
> (I'll mention up front that NFSv3 works perfectly -- only NFSv4 is bad.) |
| 8 |
> |
| 9 |
|
| 10 |
this is due to different authentication methods used in nfs3 and nfs4 and does |
| 11 |
not rely on installation arch (32/64bit). you have to tune up nfs4 |
| 12 |
infrastructure. on both client and server make sure you have |
| 13 |
|
| 14 |
- nfs4 and inotify support in kernel |
| 15 |
- net-fs/nfs-utils installed with nfs4 support |
| 16 |
- grep NFS_NEEDED_SERVICES /etc/conf.d/nfs shows 'NFS_NEEDED_SERVICES="rpc.idmapd"' |
| 17 |
- grep Domain /etc/idmapd.conf shows 'Domain = <your local domain>' |
| 18 |
- rpc.idmapd daemon is running (if it does not, restart nfs stack) |
| 19 |
- surely portage uid/gid are the same on all nfs-ed machines |
| 20 |
|
| 21 |
server side: |
| 22 |
/etc/exports: /usr/portage |
| 23 |
192.168.1.0/24(async,no_root_squash,rw,no_subtree_check) |
| 24 |
|
| 25 |
client side: |
| 26 |
grep nfs /etc/fstab: server:/usr/portage /usr/portage nfs4 defaults,rw 0 1 |
| 27 |
|
| 28 |
consult rpc.idmapd(8) for details |
| 29 |
|
| 30 |
that way i'm sharing portage at home. works pretty good for months i've migrated |
| 31 |
to nfs4 |
| 32 |
|
| 33 |
hth |
Archives