Re: klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine

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

 



On Wed, 2009-04-15 at 12:50 +0200, Hans-Peter Jansen wrote:
> Hi,
> 
> I suffer from a problem, where my diskless environment doesn't work anymore 
> after upgrading the server from openSUSE 11.0 (2.6.25.20) to openSUSE 11.1 
> (2.6.27.21).
> 
> The diskless environment gets set up with an customized initrd via pxelinux.
> The initrd uses klibc's nfsmount, and I've tried both protocols: udp and 
> tcp. It's not an iptables issue, since I can mount these directories from 
> other (fully booted) systems just fine. 
> 
> Using the debug version of klibc's nfsmount prints these messages:
> short read: 0 < 28
> Port for 100003/3[udp]: 0
> short read: 0 < 28
> Port for 100005/3[udp]: 0
> NFS params:
>   server = xxx.xx.xx.xx, path = "/roroot", version = 3, proto = udp,
>   mount_port = 627, nfs_port = 2049, flags = 00010282,
    ^^^^^^^^^^^^^^^^

>   rsize = 0, wsize = 0, timeo = 7, retrans = 3,
>   acreg (min,max) = (3,60), acdir (min,max) = (30,60),
>   soft = 0, intr = 1, posix = 0, nocto = 0, noac = 0
> 
> tcpdumping the communication shows, that for whatever reason, the client 
> sends the mount request from source port 798 to destination port 627, but 
> the server doesn't listen on 627:

The question is why is klibc specifying mount port = 627?

Trond

--
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