similar to: Setting up NFS on Centos 6.6

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, I'm running CentOS 6.5 as NFS server (v3 and v4) and exporting Ext4 and XFS filesystem. After many months that all works fine today the server crash: Jan 30 09:46:13 qb-storage kernel: ------------[ cut here ]------------ Jan 30 09:46:13 qb-storage kernel: WARNING: at lib/list_debug.c:26 __list_add+0x6d/0xa0() (Not tainted) Jan 30 09:46:13 qb-storage kernel: Hardware name: PowerEdge

When we decide not use zero-copy, msg.control should be set to NULL otherwise macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs wrongly. Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84 (vhost-net: skip head management if no outstanding). This solves the following warnings: WARNING: at include/linux/kref.h:47 handle_tx+0x477/0x4b0 [vhost_net]()

When we decide not use zero-copy, msg.control should be set to NULL otherwise macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs wrongly. Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84 (vhost-net: skip head management if no outstanding). This solves the following warnings: WARNING: at include/linux/kref.h:47 handle_tx+0x477/0x4b0 [vhost_net]()

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

Hi All, I am looking for advice on how to cure a constantly-crashing NFS server which crashes every few hours, or at least, every few days. The kernel log file (below) points toward NFS as a likely cause. The system disk is a 3ware 8000 series RAID1 mirror. The data disk is using a 3Ware 9000 controller to produce two RAID1 devices; these are then striped (RAID0) in software to form a RAID 10

Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut

I installed ovirt-agent on a fresh fedora 11 install (not in a virtual machine). The only thing I modified prior to installation was /etc/resolv.conf in order to be able to yum update and install the ovirt packages via yum (from the ovirt repo), and /etc/ntp.conf to get the correct time from the NTP server of my network. I also disabled NetworkManager via chkconfig. I used all the options for

In the old days NFS Shared Path had a static handle (ie a number), normal based on some number pulled out of the file system/inode. To fix (well work around) a security issue, for about 10+ years now, when a NFS server reboots, it generates a new random handle for the NFS Share. (sever may generate a new random handle per mount request) The NFS Stale Handle happens when the client is still

Hello, Please CC replies I'm not subscribed. Performance with samba and only samba degrades terribly when we use the bonding driver to aggregate two ethernet cards. Instead of a steady file copy it seems to go in spurts. If I pull out one of the network cables (doesn't matter which) performance resumes to full speed. I can pull the cable in the middle of a transfer and it will go

Hi, Since upgrading to "2.6.18-194" I am getting odd messages in the logs. Such as; sraid3 kernel INFO task pdflush 259 blocked for more than 120 seconds. The output from > grep '120 seconds' /var/log/messages | tr : ' ' | awk '{print $10}' | sort | uniq -c 6 nfsd 4 pdflush This is from an NFS server that since the upgrade has been

CentOS 6.4 x86_64 Kernel: 2.6.32-358.14.1.el6.x86_64 I have been noticing repeatedly that after a couple of weeks of uptime my NFS server starts to generate the following error: ------------[ cut here ]------------ WARNING: at lib/list_debug.c:26 __list_add+0x6d/0xa0() (Tainted: G W ---

Good Morning, I have successfully deployed Ovirt manager and 1 node (1.03 version). All networks interfaces work fine. When I try to configure a NFS storage, the web interface gives a timeout agent error and on the node in /var/log/messages I read the following lines: FATAL: Error inserting nfsd (/lib/modules/2.6.30.5-43.fc11.x86_64/kernel/fs/nfsd/nfsd.ko): Unknown symbol in module, or

On 06/05/2013 09:44 PM, Sergei Shtylyov wrote: > Hello. > > On 05-06-2013 11:40, Jason Wang wrote: > >> When we decide not use zero-copy, msg.control should be set to NULL >> otherwise >> macvtap/tap may set zerocopy callbacks which may decrease the kref of >> ubufs >> wrongly. > >> Bug were introduced by commit

On 06/05/2013 09:44 PM, Sergei Shtylyov wrote: > Hello. > > On 05-06-2013 11:40, Jason Wang wrote: > >> When we decide not use zero-copy, msg.control should be set to NULL >> otherwise >> macvtap/tap may set zerocopy callbacks which may decrease the kref of >> ubufs >> wrongly. > >> Bug were introduced by commit

What's the procedure for filing bug reports related to kernel panics on CentOS/RHEL? I've just had the following kernel panic on one of the new mailstores (argh!). Would this have to be reproduceable to warrant a bug report? Feb 28 14:40:53 tempmailstore1a kernel: eip: c0146a64 Feb 28 14:40:53 tempmailstore1a kernel: eip: c0146a64 Feb 28 14:40:53 tempmailstore1a kernel: ------------[ cut

Our Tyan VX50 server, which is otherwise stable, can be crashed by a specific user who starts a Java application. Relevant facts are: x86_64 CentOS 4.3 fully updated (but otherwise default config) 8 Dual-Core Opteron 870 (2 GHz), giving 16 cores 32 GB memory (running at DDR333) The panic is reproducible within a couple of minutes. I tried the 2.6.9-42 largesmp kernel from J.Baron's website

Hi everybody, i hope that i'm on the right mailing list. I'm having some trouble with xfs and xen. We are running the newest xenserver version with ha on dell servers and a dell equalogic. I set up a fileserver (debian lenny 2.6.29-xs5.5.0.17) with one ext3 partiton for the os and one xfs partition for the data. Two webserver are using this fileserver with nfs. Now i run the second

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Not strictly Asterisk related, but I'm trying to get an AVM Fritz! card to work with Asterisk on a Fedora Core 3 box. I've grabbed the official AVM Fritz CAPI driver from the AVM website and compiled against the current kernel. However, as soon as I modprobe it I get: CAPI Subsystem Rev 1.1.2.8 fcpci: module license 'Proprietary'