[22:45] <blkperl> slangasek: so the automounter seems to hanging on mount commands in Trusty
[22:45] <blkperl> which is why its so slow...
[22:45]  * blkperl tests to see if precise has the same issue
[22:45] <slangasek> blkperl: hi! how're things?
[22:46] <blkperl> pretty good
[22:46] <slangasek> blkperl: have you applied to the Debian NM queue yet?
[22:46] <slangasek> so you can fix Debian? :)
[22:46] <slangasek> anyway
[22:46] <slangasek> which automounter are we talking about?  autofs?
[22:46]  * blkperl bets its a nfsv4 issue
[22:46] <blkperl> yeah autofs
[22:46] <blkperl> I strace'd and it was just hanging on mount
[22:47] <slangasek> on a booted system?
[22:47] <blkperl> well a freshly rebooted system
[22:47] <slangasek> and is it hanging on a mount syscall or a mount command?
[22:47] <slangasek> right, my point is, you're stracing it from runlevel 2 rather than trying to strace it in the boot sequence, yah?
[22:47] <blkperl> no the system is fully up at this point, so runlevel 5
[22:48] <blkperl> with GUI and everything
[22:49] <blkperl> execve("/bin/mount", ["mount", "vault.cat.pdx.edu:/volumes/bunga"..., "/mnt"], [/* 22 vars */]) = 0
[22:49] <blkperl> is that syscall or mount command?
[22:50] <blkperl> looks like mount right?
[22:51] <blkperl> [pid  2516] mount("vault.cat.pdx.edu:/volumes/bungalow/09/blkperl/ubuntu", "/mnt", "nfs", 0, "vers=4,addr=131.252.208.194,clie"...
[22:52] <blkperl> ok so it goes into the kernel there ^ and hangs
[22:52] <slangasek> "runlevel 5"?  using Red Hat runlevel emulation, hmmm?
[22:52] <slangasek> that's the mount command
[22:52] <blkperl> ok
[22:53] <blkperl> how do i figure out whats its waiting on?
[22:53] <slangasek> which in turn calls the mount() syscall, but my question was whether it was a sycall called directly by autofs or via mount
[22:53] <slangasek> well, for starters I would suggest running strace -s256 so you can see the full command it's running
[22:53] <blkperl> I can reproduce with mount command without stracing autofs
[22:53] <slangasek> and then try to reproduce from the commandline with 'mount' instead of autofs
[22:53] <slangasek> ok
[22:54] <slangasek> are you sure you're passing all the same options autofs is?
[22:54] <slangasek> because it's entirely possible to have mount from the commandline hanging for a *different* reason
[22:54] <slangasek> (and can I see the full commandline please)
[22:54] <blkperl> haha, no im not sure but they are both using nfsv4
[22:54] <blkperl> strace -f -s256 mount vault.cat.pdx.edu:/volumes/bungalow/09/blkperl/ubuntu /mnt
[22:55] <blkperl> -s256 is awesome btw
[22:55]  * blkperl <3s new flag
[22:55] <slangasek> was looking for the strace on autofs itself though, to be sure we capture exactly which mount options it's passing
[22:55] <blkperl> will do
[22:55] <slangasek> kerberos authentication?  Solaris or Linux server?
[22:55] <blkperl> Solaris server, no kerby
[22:56] <blkperl> [pid  2598] mount("vault.cat.pdx.edu:/volumes/bungalow/09/blkperl/ubuntu", "/u/blkperl", "nfs", MS_NOSUID, "hard,intr,sloppy,vers=4,addr=131.252.208.194,clientaddr=131.252.213.23"
[22:56] <blkperl> automount is using those args
[22:58] <slangasek> ok; those are largely defaults autopopulated by mount internally, or near enough as to make no difference
[22:58] <slangasek> I guess I shouldn't expect this mount command to work for me from here? ;)
[22:58] <blkperl> nope :)
[22:59] <slangasek> so first, I'd check whether it also happens with -o nfsvers=3
[22:59] <slangasek> I think it was between precise and trusty that the default changed
[23:03] <blkperl> slangasek: yeah vers=3 is fast
[23:04] <blkperl> vers=4 hangs
[23:04] <slangasek> blkperl: ok, so
[23:04] <slangasek> tcpdump
[23:04] <slangasek> nfs4 and nfs3 use different ports, etc.; you'll want to see if it's a firewall problem
[23:08] <blkperl> hmm is there any easy way to parse this output for NFS ?
[23:16] <blkperl> slangasek: doesn't look any firewall issues
[23:21] <blkperl> hmm can't reproduce now...
[23:23] <blkperl> if you turn on RPC debugging mount works fine
[23:23] <blkperl> super helpful....
[23:36] <slangasek> blkperl: parsing which output?  tcpdump?
[23:37] <slangasek> blkperl: I actually meant 'tcpdump -s 1500 -w send-me-a.pcap', fwiw :)
[23:37] <blkperl> slangasek: im starting to get suspicous thats it an ipv6 thing
[23:37] <slangasek> that would be interesting
[23:37]  * blkperl tries to reproduce one more time
[23:38] <blkperl> its totally ipv6
[23:38] <blkperl> stupid slac addresses
[23:50] <blkperl> or maybe not I don't see any ipv6 traffic
[23:54] <slangasek> well, your strace specifically showed ipv4 addresses in use
[23:54] <slangasek> and the server has no ipv6 in public DNS
[23:54] <blkperl> thats true
[23:54] <slangasek> also
[23:54] <slangasek> HAHAHA NEXENTA
[23:55] <slangasek> I assumed you meant real Solaris, not Nexenta crazytown
[23:55] <blkperl> well its both, really, homedirs come from nexenta and pkgs come from solaris11
[23:56] <blkperl> oh thats cool... hanging on rebooting
[23:57] <slangasek> let me know if Nexenta is still violating the GPL with respect to code written for Debian
[23:57] <blkperl> oh im sure they are...
[23:57] <blkperl> how did you know it was nexenta?