Re: [BUG?] Maybe NFS bug since 2.6.37 on SPARC64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lukas Razik wrote:

  The next thing is:
  Really all working kernels (<=2.6.36.4) first output
   Looking up port of RPC 100003/2 on 137.226.167.241
  then
   Looking up port of RPC 100005/1 on 137.226.167.241
  and then the mount is successful
   VFS: Mounted root (nfs filesystem) on device 0:15.
  
  So what about >=2.6.37?
  Why don't these kernels try other ports, too?
  Or why do the old kernels try more than one port?
  Why is there no output (even in the nfsdebug mode) that the kernel tries to connect to the RPC service?
  Is there a "easy" possibility to change port 100003 to 100005 in >=2.6.37?

Those are the rpc numbers.  The kernel is trying to find the port numbers
for those services.  100003 is nfs, 100005 is mount.  I guess at this point
I would use wireshark to find out what requests are actually being made and
responded to in both cases.  Are you sure portmap is working on the server
and not being blocked by a firewall?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux