similar to: NFS between domU and dom0 causes the virtual network to freeze! Please help

Greetings, I have problem using Dom0 as NFS(v4)-server and DomU as client. When ever the client actually tries to copy data to nfs-server the virtual network (bridge) between the two hosts completely freezes and stops working. After this of course the client hangs waiting nfs-server to answer and server continues to try to contact nfslock daemon on the client. Dom0 is still accessible from

I''ve locked up my dom0 a couple of times this morning copying a 3GB file from local disk to an NFS mount(neither xend nor guests running). I don''t encounter this problem on the stock CentOS 4 kernel. The machine is a PowerEdge 2850 with 2 e1000 cards - the one in use is connected to a PowerConnect 2216 10/100 switch and has negotiated 100Mbit. I''ll check if the stock

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:

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

We have a Xen 3.0 / Linux kernel 2.6.15 machine with the domU''s configured for shared /home directories. One of the domU''s is an NFS server, exporting /home, and the other domU''s all mount this. It all functions fine, but it''s pretty slow. I tried untarring a recent Linux kernel tarball. On the NFS server domU this takes about 25 seconds. I didn''t

hi, guys: Today when i typed "mount " command on the server and found this message: .. ... 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs (

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

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)

Hi all, I'm migrating from Gentoo to CentOS... I'm experiencing a rather low performance in NFS r/w (as client). NFS server is solaris (which exports zfs volumes via nfs). The very same exports were mounted with the same parameters (auto,nosuid,exec) on gentoo and centos server (bot x86_64)... It happens that centos is 5-10 times slower either in read and write operations... Ok,

Hello, Does anybody know how to avoid the file fragmentation when a file is created over NFSv3? A file created locally is OK: dd bs=32k if=/dev/zero of=test count=32x1024 conv=fsync filefrag test test: 10 extents found, perfection would be 9 extents When I create the file in the same dir, but from another machine, mounted over NFS: filefrag test test: 4833 extents found, perfection would be

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

Hi all, This is my first post to the list, I hope someone out there can help! I am running xen 3.0.3, with CentOS 5.2 based Dom0 (kernel-xen-2.6.18-92.1.22.el5) Recently I have noticed some complete system lockups on a few different servers. Neither Dom0 or any of the guests respond to pings, connecting a keyboard and monitor to the system only shows a blank screen. Nothing is written to logs

This seems like another basic question because I always assumed that if I threw something in my /etc/fstab then it will be automatically mounted at boot time (unless I put in the 'noauto' option). But my NFS partition isn't getting mounted, here's the excerpt from my /etc/fstab file, split on the whitespace so it's easier to read: nfs_server:/exports/var/www /var/www nfs

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 \

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

The number of threads has nothing to do with the number of cores on the machine. It depends on the I/O, network speed, type of workload etc. We usually start with 32 threads and increase if necessary. You can check the statistics with: watch 'cat /proc/net/rpc/nfsd | grep th? Or you can check on the client nfsstat -rc Client rpc stats: calls retrans authrefrsh 1326777974 0

Greetings all- I have a CentOS 5 (Final) system that is serving up content to several other hosts via NFS. The amount of data transferred is rather small as most of the files are under 100kb and each export has maybe 100 files that are accessed regularly. I'm finding that as I add more hosts accessing the NFS server, the performance seems to be getting poorer. There are obvious delays when

Hi I use rsync for daily backups from a mailserver. Every day the mailserver pushes backup to the backupserver. Cron runs the command: rsync -q -zrlpt --specials --chmod=Du+rwx \ --rsh 'ssh -F /root/ssh/config -i /root/ssh/private.key -o UserKnownHostsFile=/root/ssh/known_hosts' \ --files-from=/root/include \ --exclude-from=/root/exclude \ --link-dest=../previous \ /

This may not be a CentOS problem, because I'm in a mixed environment. But I put it out in case anybody has any thoughts. I recently replaced a file server, which was on a Pentium III based system running 32-bit CentOS 4.3, with an Opteron based system running Fedora 4. The NFS clients are all CentOS 4.3, some are 32 bit and some are 64 bit. Since the replacement, when I try to write