similar to: OCFS2 & Using the private interconnect with jumbo frames for heartbeat

OEL 5, OCFS 1.4, using EMC Power Path for multi pathing. I want t mount the OCFS2 file system on the emc power path device. I can mount by UUID, and not have to worry about persistent bindings across nodes. But how do I make sure when it mounts by UUID , that the pwoer path device is used. Any help will be much appreciated. Thanks -- Sridhar Avantsa savantsa at gmail.com -------------- next

Hi, Has anyone using CentOS 6 been able to successfully set an mtu larger than 9710 on an interface. I am seeing super jumbo frames with length > 10000. ... IP 10.79.4.53.64327 > 10.79.2.53.24294: Flags [.], seq 16060:29200, ack 1, win 32767, length 13140 ... CentOS release 6.7 (Final) Thanks, -- Stephen Clark *NetWolves Managed Services, LLC.* Director of Technology Phone:

Hello, I have 2 network cards on my 2 of my computers that I am trying to transfer data on. The second network cards are specifically for transferring files between the two so I enabled jumble frames by setting the mtu to 9000. I seem to be able to connect between the two via ssh and other methods using this setting so I thought everything was working right until I tried rsync. I used the

The documentation says the bridge will work as far as all interfaces have the same MTU, but I also read on this and other mailing lists people having problems when using jumbo frames. What is the current status of jumbo frames support in the bridge? It could also be useful to have the same info on the wiki page. Thanks. -- Luca Lesinigo -------------- next part -------------- An HTML

Hi, I have an XCP 0.5 box running a few DomUs some of the DomU''s data is stored at (clustered lvm volumes on) a Coraid etherdrive box which is connected via an Ethernet cable to a dedicated card of the XCP box, for which in the network config I'' ve specified: MTU=9344: xe network-param-list uuid=.... gives: MTU ( RW): 9344 on the DomUs if I leave the MTU at 1500 (default

On 11/09/2015 12:36 PM, Gordon Messmer wrote: > On 11/09/2015 08:34 AM, Steve Clark wrote: >> Has anyone using CentOS 6 been able to successfully set an mtu larger >> than 9710 >> on an interface. > Maximum frame size varies from implementation to implementation: > http://pages.uoregon.edu/joe/jumbo-clean-gear.html > > It's also worth noting that that due to

Hi everyone, I have looked through the list archives and seen a few posts about jumbo frame support, but there is no definitive answer on whether or not it has been tested or is working for anyone. I tried using an MTU of 9000 in a domU and encountered some very interesting and not-so-great results. My machines used in this test are: * NFS (physical) * dom0 (physical) * domU (virtual)

After successfully getting higher MTU to work on my Realtek NICs, I started testing the impact of higher MTU on file transfers using NFS exported ramdisk to ramdisk. The results were unexpected. The higher the MTU on the sending NIC, the lower the file transfer speed. I tested by using time cp to copy a 1GB file (In case compression might affect the results, so I dd the test file from the CentOS

Hello all, Not sure if I am completely missing something but here goes. I have XCP 1.0 running without any issues. I have the mtu set on both the storage network, the corresponding PIF, and the VIF to 9000 and when displayed in ifconfig it shows that this is indeed true. I have several CentOs 5.6 VMs running in HVM mode (i.e. no xen kernel) which attach to the the storage network through these

We are utilizing the xen hypervisor on nexenta with ISCSI as our method of communication with the guests (currently ubuntu but could be moving to centos). Obviously jumbo packet support would be nice to have. The last time I see that on the xen roadmap http://wiki.xensource.com/xenwiki/XenRoadMap . Is there a canonical place that spells out if jumbo frames are now supported or still on the

I have an OCFS2 filesystem on a coraid AOE device. It mounts fine, but with heavy I/O the server self fences claiming a write timeout: (16,2):o2hb_write_timeout:164 ERROR: Heartbeat write timeout to device etherd/e0.1p1 after 12000 milliseconds (16,2):o2hb_stop_all_regions:1789 ERROR: stopping heartbeat on all active regions. Kernel panic - not syncing: ocfs2 is very sorry to be fencing this

On the network theme again. The adapters on the management/storage network all default to an mtu of 1500. Are there plans to be able to indicate when a network supports jumbo frames? Cheers, Justin.

I was trying to do some performance testing between using iSCSI on the host as a diskfile to a guest vs the VM guest using the iSCSI device directly. However, in the process of trying to establish a baseline performance figure, I started increasing the MTU settings on the PCI-express NICs with RTL8168B chips. First bottleneck was discovering the max MTU allowed on these is 7K instead of 9K but

Hi, Increasing MTU beyond 1500 in Linux dom0 results in ooopses. I did not find any statement whether 2.0 series support jumbos or not in dom0. Does it? TIA, Teemu -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello Everyone, We are looking to interconnect with a local ILEC over an OC-n transport layer. They basically gave us two options in terms of mapping the SONET to the DS3: * VT1.5s mapping * DS1s mapping The second option is quite clear. We would MUX the connection, and plug the lines into qaud t1 cads etc... The tech mentioned that with the second option we would also need a DACS to convert

Hello folks. We are trying to interconnect an asterisk installation with a gnugk 2.0.5 installation to become able to use some H323 hardware that needs a gatekeeper (particulary an Ericsson WebSwitch 100). We have managed asterisk to dial H323 endpoints successfully (although calls are interrupted immediately after connection with "spawn extension exited non-zero"), but we could not

I would like to use jumbo frame for local interfaces, but I am not sure in which order to set it up. Should it be set on the physical interface first, then on the bridge and on the guest, or in another way? On some servers there are configurations with vlan on the bridge

Hello again. Our production cluster has begun experiencing some vicious slowdowns that may (or may not) be related to the filesystems. When the problem occurs, the load average on the servers jumps up to 30 or higher. Usually one node will climb while the other drops, then they will switch places a few minutes later. At one point, we had one node's load average up over 300. Our site

We have a cluster (212 nodes) that are on a gig-e network useing jumbo frames (mtu 6000) To reload a node we have to plug it into a regular 1500 mtu that is running off a differnt port on the head node to install. Is there a way to tell in the 'append' line of /pxelinux.cfg/default to have the bcm5700 module run wiht jumbo frames. this is our append right now append load_ramdisk=1

On 11/09/2015 08:34 AM, Steve Clark wrote: > > Has anyone using CentOS 6 been able to successfully set an mtu larger > than 9710 > on an interface. Maximum frame size varies from implementation to implementation: http://pages.uoregon.edu/joe/jumbo-clean-gear.html It's also worth noting that that due to offloading features in modern NICs, there's often very little benefit