similar to: NFSroot is acting strange in CentOS5

Hello all, Though the question is NFS-related, it is in conjunction with the PXE booting. Issue/Scenario: - PXE/DHCP/NFS and tFTP server running CentOS51 and is configured per PXE/Syslinux and RHEL diskless workstation documentation. 1. Attempt to test ability for client to PXE boot over the network and run Root-NFS 2. NFS export in the PXE server is: # # NFS Export Files for qatest1 host #

Peter, we found that nfs over udp will corrupt data under very extrem load, there is no way to fix it due to the way how UDP works. TCP will not have these problems. I also wonder why the package size is only 1k. Everyone who wishes a slow connection can pass the desired options via the kernel cmdline. Everyone else prefers probably the fast mount. The defaults should look more like that: ---

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

I set up a 3.3 gluster volume for another sysadmin and he has added it to his cluster via automount. It seems to work initially but after some time (days) he is now regularly seeing this warning: "Too many levels of symbolic links" $ df: `/share/gl': Too many levels of symbolic links when he tries to traverse the mounted filesystems. I've been using gluster with static mounts

The in-kernel nfsroot code is obsoleted by kinit. Remove it; it causes conflicts. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 161e1dc16ec1129b30b634a2a8dcbbd1937800c5 tree c30da837d746fe65d8a13ccf6f27bd381948edb4 parent 018604e070e143657abcf0cb256a1e2dda205d97 author H. Peter Anvin <hpa at zytor.com> Sat, 20 May 2006 16:24:05 -0700 committer H. Peter Anvin <hpa at

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`. How to reproduce: 1) Cabling: server <=> 100 Mbps switch <=> client Alternatively, one can use a 1000 Mbps switch and

I have been experimenting exporting btrfs subvolumes over nfs. Main subvolume is filesys1 mounted at /filesys1. Below this is subvolume base, user1 is in base and documents is in user1. documents is mounted at /documents. /etc/exports is: /filesys1/base/user1 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /filesys1/user1-snapshot 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0)

Hello I have a problem with Invalid data System debian10 dovecot-2.2.36.4 # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10 Oct 23 15:57:52 dovecot6 dovecot: lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file /vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data: In debian9 -

hi, i trying to install a fai installation server in a DomU for DomUs, but i have some problems with nfs. The DomUs says, that they can''t reach the NFS Server =========== Begin: Retrying nfs mount ... IP-Config: eth0 hardware address 00:16:3e:7a:25:7c mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.16.0.255 IP-Config: eth0 complete (from 172.16.0.151): address:

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 initially written, the default rsize/wsize were much lower, which matched the timeo=7. Now they cause the lags/timeouts that I reported. So

I have several machines, same hardware and config, but one tiny little change.. the hostname. Each one of these diskless machines needs its own hostname. Presently my pxelinux.cfg is setup like: prompt 1 default Gentoo timeout 10 label Gentoo kernel boot/kernel-3.16.5-gentoo APPEND root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.10:/RAID/diskless/XXXXX-mythtv-0.27-fixes,tcp,rsize=131072

Hi, I've got another one... NFS error 101 with NFSROOT has been discussed a lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, and I suspect my diskless box does not set its IP parameters right. PXElinux is set up as follows: label linvdr kernel kernel-linvdr append initrd=initrd-linvdr acpi=off root=/dev/nfs \

Yes, multiple imap servers using one shared nfs storage. With the same config on 2.2.13 the public interface traffic was similar to the storage interface, around 100 mbps. After we switch to 2.2.27 the storage interface traffic jumped 10 times while the public interface stayed the same. This make us thinking that something is wrong and each time a user logs in the whole Inbox content is read

Hi, I hit a bizare problem with dovecot 2.2.7 on debian 9 with LMTP enabled and auth/penalty disabled as documented here : https://wiki.dovecot.org/Authentication/Penalty Use case : I run a swaks command to send an email to an exim4 that tries to make a callout to dovecot-lmtp. At RCPT TO: swaks hangs 5.0<something-small> seconds then process normally (exim is waiting for callout

Hello. We have a number of Xen 3.4.2. boxes which have constant iowaits at around 10% with spikes up to 100% when accessing data over NFS. We have been unable to nail down the issue. Any advice? System info: release : 2.6.18-194.3.1.el5xen version : #1 SMP Thu May 13 13:49:53 EDT 2010 machine : x86_64 nr_cpus : 16 nr_nodes

Hi all, 1) My NFS3 clients don't display or obey existing non-POSIX ACLs on files of NFS3-mounted exports. 2) setfacl on the client throws error and fails : # setfacl -m u:stowler:rw testfile.text setfacl: testfile.text: Operation not supported 3) at time of client mount the server's /var/log/messages shows "kernel: svc: unknown version (3)". Any thoughts greatly

On Wed, Oct 10, 2018 at 09:37:46AM +0300, Aki Tuomi wrote: > > > On 09.10.2018 22:16, William Taylor wrote: > > We have started seeing index corruption ever since we upgraded (we > > believe) our imap servers from SL6 to Centos 7. Mail/Indexes are stored > > on Netapps mounted via NFS. We have 2 lvs servers running surealived in > > dr/wlc, 2 directors and 6

Hi, I can confirm that in the bad behavior, the 5 second delay occurs at each AUTH in our case. I think the configuration we have kill auth process at each end of AUTH (and fork a new one for next next AUTH). I think the "disable" flag is local to the process that is killed / respawned. A collegue of mine, Laurent Guerby, has found a workaround for us and it's findings seems

Hi everyone Version 4.0.0alpha18-GIT-bfc7481 openSUSE 12.1 Conventional nfs4 export works fine, but I'm having trouble kerberizing it for Samba 4 for my Samba 4 users. I've setup the nfs4 pseudo stuff like this: hh3:/ # mkdir /export hh3:/ # mkdir /export/home hh3:/ # mount --bind /home /export/home Here is /etc/exports: /export

HI All, We have a couple of dovecot director proxies and six backed mailstores each accessing mailboxes stored on five NFSv4 filsystems with about 1TB of mail on each in maildir format.? We have about 800 max users on each mailstore at peak times and performance appears to starting to degrade at these times.? The mailstores are pretty recent hardware with 64GB of RAM and 24 cores.?? The NFS