I was testing ocfs2 on a 2 node cluster set up.
ocfs2-tools version is 1.6.3
ocfs2 kernel version is 2.6.36
Using cman on 2 nodes
node02 dw # ping_pong -rwm /data/test.dat 3
data increment = 2
14 locks/sec
node01 dw # ping_pong -rw /data/test.dat 3
data increment = 2
10 locks/sec
node02 dw # ping_pong -r /data/test.dat 3
1980 locks/sec
Using cman on 1 node
node02 dw # ping_pong -rwm /data/test.dat 3
data increment = 1
3165 locks/sec
node02 dw # ping_pong -rw /data/test.dat 3
data increment = 1
3289 locks/sec
node02 dw # ping_pong -r /data/test.dat 3
3267 locks/sec
The above seems reasonable and behaved as expected when the program was
stopped and started repeatedly on either node. So it passed the test.
Unfortunately o2cb didnt behave as expected.
Using o2cb on 2 nodes
node02 dw # ping_pong -rwm /data/test.dat 3
data increment = 199
data increment = 76
data increment = 1
data increment = 117
data increment = 84
data increment = 1
data increment = 212
data increment = 211
data increment = 1
data increment = 225
data increment = 85
data increment = 1
data increment = 237
data increment = 158
data increment = 1
data increment = 75
data increment = 235
data increment = 1
data increment = 199
data increment = 4
data increment = 1
171803 locks/sec
and occasionally you will get the data increment remaining at 1 when 2 nodes
have joined
node02 dw # ping_pong -rw /data/test.dat 3
data increment = 2
45 locks/sec
node01 dw # ping_pong -r /data/test.dat 3
2155175 locks/sec
Using cman on 1 node
node02 dw # ping_pong -rwm /data/test.dat 3
data increment = 1
2230553 locks/sec
node02 dw # ping_pong -rw /data/test.dat 3
data increment = 1
299492 locks/sec
node02 dw # ping_pong -r /data/test.dat 3
2249787 locks/sec
The mmap test failed. The read/write test 'usually' worked but
frequently
didn't increment the 'data increment' to 2, when the program was
running on
both nodes.
Any suggestions why this isn't working as expected?
Thanks, Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110117/6a1f7db6/attachment.html
ping_long tests the fcntl() user locks. ocfs2 supports clustered fcntl() locking with cman and pacemaker cluster stacks. Not with o2cb. ocfs2 supports clustered flock() with all stacks. o2cb, cman and pacemaker. On 01/17/2011 07:25 AM, Dan Warner wrote:> I was testing ocfs2 on a 2 node cluster set up. > > ocfs2-tools version is 1.6.3 > ocfs2 kernel version is 2.6.36 > > Using cman on 2 nodes > > node02 dw # ping_pong -rwm /data/test.dat 3 > data increment = 2 > 14 locks/sec > > node01 dw # ping_pong -rw /data/test.dat 3 > data increment = 2 > 10 locks/sec > > node02 dw # ping_pong -r /data/test.dat 3 > 1980 locks/sec > > Using cman on 1 node > > node02 dw # ping_pong -rwm /data/test.dat 3 > data increment = 1 > 3165 locks/sec > > node02 dw # ping_pong -rw /data/test.dat 3 > data increment = 1 > 3289 locks/sec > > node02 dw # ping_pong -r /data/test.dat 3 > 3267 locks/sec > > The above seems reasonable and behaved as expected when the program was stopped and started repeatedly on either node. So it passed the test. > > > > Unfortunately o2cb didnt behave as expected. > > Using o2cb on 2 nodes > > node02 dw # ping_pong -rwm /data/test.dat 3 > data increment = 199 > data increment = 76 > data increment = 1 > data increment = 117 > data increment = 84 > data increment = 1 > data increment = 212 > data increment = 211 > data increment = 1 > data increment = 225 > data increment = 85 > data increment = 1 > data increment = 237 > data increment = 158 > data increment = 1 > data increment = 75 > data increment = 235 > data increment = 1 > data increment = 199 > data increment = 4 > data increment = 1 > 171803 locks/sec > > and occasionally you will get the data increment remaining at 1 when 2 nodes have joined > > node02 dw # ping_pong -rw /data/test.dat 3 > data increment = 2 > 45 locks/sec > > node01 dw # ping_pong -r /data/test.dat 3 > 2155175 locks/sec > > Using cman on 1 node > > node02 dw # ping_pong -rwm /data/test.dat 3 > data increment = 1 > 2230553 locks/sec > > node02 dw # ping_pong -rw /data/test.dat 3 > data increment = 1 > 299492 locks/sec > > node02 dw # ping_pong -r /data/test.dat 3 > 2249787 locks/sec > > The mmap test failed. The read/write test 'usually' worked but frequently didn't increment the 'data increment' to 2, when the program was running on both nodes. > > Any suggestions why this isn't working as expected? > > Thanks, Dan > > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users at oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110118/affa55c3/attachment.html
OK thanks for the clarification. Is the support of fcntl() locking within o2cb, on the wishlist of features to be implemented at a future date? Is it even a priority to do? Thanks, Dan On 18 January 2011 18:00, Sunil Mushran <sunil.mushran at oracle.com> wrote:> ping_long tests the fcntl() user locks. > > ocfs2 supports clustered fcntl() locking with cman and pacemaker > cluster stacks. Not with o2cb. > > ocfs2 supports clustered flock() with all stacks. o2cb, cman and pacemaker. >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110118/b1fcd32a/attachment.html