[02:59] slangasek: the problem seems to be the automounter [03:11] slangasek: ugh nfsv4 works, nfsv3 doesn't work [03:11] but nfsv4 is sloow [03:19] also i doesn't make sense because some boxes are working with nfsv3 [07:02] blkperl: so, see https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1327563 [07:02] Launchpad bug 1327563 in linux (Ubuntu Utopic) "Long delay when mounting NFS shares" [Medium,Fix released] [07:03] I'm not sure if that's actually the bug I was looking at before, but it was fixed exactly a week ago in trusty [07:29] slangasek: oh awesome [07:29] slangasek: if so then we can use nfsv4 again === bdmurray_ is now known as bdmurray === blkperl_ is now known as blkperl [16:27] slangasek: have you seen a bug where some homedirs show up as owned by 4294967294 in ls [16:44] slangasek: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1124250 [16:44] Launchpad bug 1124250 in nfs-utils (Ubuntu) "Partially incorrect uid mapping with nfs4/idmapd/ldap-auth" [Undecided,Confirmed] [16:46] blkperl: do you happen to be passing sec=sys as a mount option? https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1315974 [16:46] Launchpad bug 1315974 in nfs-utils (Ubuntu) "NFS v3 fstab option sec=sys results in RPC AUTH_NULL credentials instead of expected AUTH_UNIX" [Undecided,New] [16:46] and are you using ldap auth for your idmap backend? [16:47] slangasek: yes and yes [16:47] ok [16:47] so maybe either one of those bugs [16:48] ok [19:48] slangasek: so /u/blkperl/.ssh is owned by user nobody when using nfsv4 but all the other files are ok :( [19:53] royal:~# nfsidmap -c [19:53] nfsidmap: fopen(/proc/keys) failed: No such file or directory [19:53] slangasek: ^ feature or bug [21:16] blkperl: I know nothing about /proc/keys