search for: georgopoulos

...nd I bumped into an NFS bug, but I'm not experienced enough to troubleshoot it more without help. If anyone can make timeo=7 work properly in 100 Mbps networks in any distribution/version, please tell me to test with that. I was testing with Ubuntu 18.04.3, kernel 4.15. Kind regards, Alkis Georgopoulos

In case anyone's interested, I followed up in the linux-nfs mailing list: https://marc.info/?l=linux-nfs&m=156887818618861&w=2 Thanks, Alkis On 9/15/19 10:51 AM, Alkis Georgopoulos wrote: > I think I got it. > > Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. > By lowering this to 32K, all issues are gone, even with the default > timeo=7. And nfsroot=xxx client responsiveness is a whole lot better. > > I think when nfsmount was init...

...ize were much lower, which matched the timeo=7. Now they cause the lags/timeouts that I reported. So please, instead of increasing timeo, decrease the default rsize/wsize to 32K. (or, where does that 1 MB default come from, so that I report it there...) Thanks, Alkis On 9/15/19 9:48 AM, Alkis Georgopoulos wrote: > I can't explain why 700 msecs aren't enough to avoid timeouts in 100 > Mbps networks, but my tests verify it, so I'm writing to the list to > request that you increase the default timeo to at least 30, or to 600 > which is the default for `mount -t nfs`. > &g...

...ents may get their ip from the wrong dhcp server (e.g. the adsl router) and fail to boot. What I'm asking for is a command line option, that forces ipconfig to ignore all DHCPOFFERs that do not have a filename option, so that it only accepts ip addresses from ltsp servers. Kind regards, Alkis Georgopoulos IP-Config: eth0 complete (from 128.131.48.127): address: 128.131.48.177 broadcast: 128.131.48.255 netmask: 255.255.255.0 gateway: 128.131.48.1 dns0 : 128.130.4.3 dns1 : 128.131.4.3 domain : itp.tuwien.ac.at rootserver: 128.131.48.127 rootpath: filename : /pxelinux.0 )

...eive a not-appropriate packet, and jump to discard_pkt, in which case it *discards* the packet and returns 0. This return value (0) will propagate to main, so (nr == 0) and packet_discard() will be called *again*, causing the NIC to wait until it happens to receive some packet. Kind regards, Alkis Georgopoulos --- usr/kinit/ipconfig/bootp_proto.c | 6 +++++- usr/kinit/ipconfig/dhcp_proto.c | 10 +++++----- usr/kinit/ipconfig/main.c | 32 +++++++++++++++++++++----------- usr/kinit/ipconfig/packet.c | 15 ++++++++++++--- 4 files changed, 43 insertions(+), 20 deletions(-) diff --git...

...unless explicitly requested. This option is passed to the kernel through struct nfs_mount_data rather than as a string, so we have to provide some value. The kernel client currently treats either 0 or UINT_MAX as requesting the default. nfs-utils passes 0, so do the same here. Reported-by: Alkis Georgopoulos <alkisg at gmail.com> References: https://lists.zytor.com/archives/klibc/2019-September/004233.html Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/kinit/nfsmount/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/usr/kinit/nfsmount/main.c b/usr/k...

...ng I don't want to do. I basically want tftpd-hpa to serve files from /var/lib/tftpboot but allow symlinks to point outside that dir. tftpd-hpa version: 5.2-1ubuntu1 cmdline: /usr/sbin/in.tftpd --listen --user tftp --address 0.0.0.0:69 --verbose /var/lib/tftpboot Kind regards, Alkis Georgopoulos

I managed to get to the bottom of this, and filed a bug report for NFS: https://bugzilla.kernel.org/show_bug.cgi?id=204939 Klibc nfsmount still a bug: it needs to NOT hardcode timeo=7. Either the NFS defaults should be used, which result in: timeo=600,rsize=1048576,wsize=1048576, or at least the kernel documented defaults, https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt