| 1 |
Bryan, |
| 2 |
Yes, I can mount just fine. I was jsut concerned that the warning |
| 3 |
was there and since I'm having trouble with |
| 4 |
bandwidth/throughput/something I was looking to make it as clean as I |
| 5 |
can. |
| 6 |
|
| 7 |
If this is not an issue I'll ignore it for now. I think my other |
| 8 |
thread about 'Lots of network collisions' is going to turn out to be |
| 9 |
the real issue. In the short term I'll record locally until I get NFS |
| 10 |
working a bit better. |
| 11 |
|
| 12 |
thanks, |
| 13 |
Mark |
| 14 |
|
| 15 |
thanks, |
| 16 |
Mark |
| 17 |
|
| 18 |
On 9/23/05, Bryan Whitehead <driver@×××××××××.net> wrote: |
| 19 |
> |
| 20 |
> Just to clarify, you can mount right? if so cat /proc/mounts on both |
| 21 |
> machines. |
| 22 |
> |
| 23 |
> can you show me the /etc/exports of the server? |
| 24 |
> |
| 25 |
> If you are able to mount you should be able to ignore the error. It looks |
| 26 |
> like everything is setup ok... unless you have firewall/iptables in the |
| 27 |
> way of any packets... |
| 28 |
> |
| 29 |
> On Fri, 23 Sep 2005, Mark Knecht wrote: |
| 30 |
> |
| 31 |
> > On 9/23/05, Dave Nebinger <dnebinger@××××.com> wrote: |
| 32 |
> >>> you don't have rpcinfo? that is not right! |
| 33 |
> >> |
| 34 |
> >>>> |
| 35 |
> >>>> dragonfly ~ # rcpinfo -p |
| 36 |
> >>>> -bash: rcpinfo: command not found |
| 37 |
> >>>> dragonfly ~ # slocate rcpinfo |
| 38 |
> >>>> dragonfly ~ # |
| 39 |
> >> |
| 40 |
> >> Hold on guys, notice the spelling difference - rpcinfo which is what you |
| 41 |
> >> need, but rcpinfo is what was searched for. |
| 42 |
> >> |
| 43 |
> > |
| 44 |
> > My bad eyes. Thanks for seeing that Dave! |
| 45 |
> > |
| 46 |
> > OK, on the Myth backend client side: |
| 47 |
> > |
| 48 |
> > dragonfly ~ # rpcinfo -p |
| 49 |
> > program vers proto port |
| 50 |
> > 100000 2 tcp 111 portmapper |
| 51 |
> > 100000 2 udp 111 portmapper |
| 52 |
> > 100024 1 udp 32768 status |
| 53 |
> > 100024 1 tcp 32769 status |
| 54 |
> > 100003 2 udp 2049 nfs |
| 55 |
> > 100003 3 udp 2049 nfs |
| 56 |
> > 100003 4 udp 2049 nfs |
| 57 |
> > 100003 2 tcp 2049 nfs |
| 58 |
> > 100003 3 tcp 2049 nfs |
| 59 |
> > 100003 4 tcp 2049 nfs |
| 60 |
> > 100021 1 udp 32770 nlockmgr |
| 61 |
> > 100021 3 udp 32770 nlockmgr |
| 62 |
> > 100021 4 udp 32770 nlockmgr |
| 63 |
> > 100021 1 tcp 32770 nlockmgr |
| 64 |
> > 100021 3 tcp 32770 nlockmgr |
| 65 |
> > 100021 4 tcp 32770 nlockmgr |
| 66 |
> > 100005 1 udp 786 mountd |
| 67 |
> > 100005 1 tcp 789 mountd |
| 68 |
> > 100005 2 udp 786 mountd |
| 69 |
> > 100005 2 tcp 789 mountd |
| 70 |
> > 100005 3 udp 786 mountd |
| 71 |
> > 100005 3 tcp 789 mountd |
| 72 |
> > dragonfly ~ # |
| 73 |
> > |
| 74 |
> > |
| 75 |
> > myth14 ~ # rpcinfo -p |
| 76 |
> > program vers proto port |
| 77 |
> > 100000 2 tcp 111 portmapper |
| 78 |
> > 100000 2 udp 111 portmapper |
| 79 |
> > 100024 1 udp 1024 status |
| 80 |
> > 100024 1 tcp 1025 status |
| 81 |
> > 100003 2 udp 2049 nfs |
| 82 |
> > 100003 3 udp 2049 nfs |
| 83 |
> > 100003 4 udp 2049 nfs |
| 84 |
> > 100003 2 tcp 2049 nfs |
| 85 |
> > 100003 3 tcp 2049 nfs |
| 86 |
> > 100003 4 tcp 2049 nfs |
| 87 |
> > 100021 1 udp 1026 nlockmgr |
| 88 |
> > 100021 3 udp 1026 nlockmgr |
| 89 |
> > 100021 4 udp 1026 nlockmgr |
| 90 |
> > 100021 1 tcp 1026 nlockmgr |
| 91 |
> > 100021 3 tcp 1026 nlockmgr |
| 92 |
> > 100021 4 tcp 1026 nlockmgr |
| 93 |
> > 100005 1 udp 889 mountd |
| 94 |
> > 100005 1 tcp 892 mountd |
| 95 |
> > 100005 2 udp 889 mountd |
| 96 |
> > 100005 2 tcp 892 mountd |
| 97 |
> > 100005 3 udp 889 mountd |
| 98 |
> > 100005 3 tcp 892 mountd |
| 99 |
> > myth14 ~ # |
| 100 |
> > |
| 101 |
> > To my UNtrained eye the two look the same. |
| 102 |
> > |
| 103 |
> > Thanks, |
| 104 |
> > Mark |
| 105 |
> > |
| 106 |
> > |
| 107 |
> |
| 108 |
> -- |
| 109 |
> Bryan Whitehead |
| 110 |
> Email:driver@×××××××××.net |
| 111 |
> -- |
| 112 |
> gentoo-user@g.o mailing list |
| 113 |
> |
| 114 |
> |
| 115 |
|
| 116 |
-- |
| 117 |
gentoo-user@g.o mailing list |
Archives