Hi All,
I have stumbled across (via Google) a post on this mailing list in relation
to performance issues with OCFS2.
A little overview of our setup:
3 x Dell Poweredge R200 servers, w/8GB RAM, Dual Gig NIC's running VSphere
4.1 (ESXi w/Enterprise License)
1 x Dell Poweredge MD3000i
Hi Somsak,
On 07/30/2010 12:54 AM, Somsak Sriprayoonsakul wrote:
Hi,
(I am in the same team with Mr. Wanchat)
Just want to note that we already format OCFS2 with -T mail option. As
note below, data=writeback,noatime, and commit interval has been
increase already.
The weird thing about
Hi,
(I am in the same team with Mr. Wanchat)
Just want to note that we already format OCFS2 with -T mail option. As note
below, data=writeback,noatime, and commit interval has been increase
already.
The weird thing about this problem is that, OCFS2 will work for like about
30 days, after that
Dear all,
Not realy sure whether this is bug or not, but we found that sometimes OCFS2
on our system do journaling a lot.
(Please see screen shot below)
As you can see, the IO was jumped from 111 w/s to 11,960 w/s , IO utilize
jumped from 1.5% to 97% , %iowait jumped from 0.25% to 10.94%.
It
Have you tried mounting with data=writeback ?
On Jul 27, 2010, at 9:31 PM, wanchat padungrat wancha...@pantip.com wrote:
Dear all,
Not realy sure whether this is bug or not, but we found that sometimes OCFS2
on our system do journaling a lot.
(Please see screen shot below)
As you can
Dear Sunil,
Thank you for your promptly reply,
Yes, we do mount as data=writeback .
following is our current mount option : type ocfs2
(rw,_netdev,noatime,commit=15,data=writeback,heartbeat=local)
Wanchat P.
2010/7/28 Sunil Mushran sunil.mush...@oracle.com
Have you tried mounting with
