Re: [Ocfs2-devel] Ocfs2-devel Digest, Vol 127, Issue 25

2014-10-09 Thread Guozhonghua
Hi Joseph and Srinivas,

We had merged and test the two patches:
1.ocfs2: o2net: set tcp user timeout to max value
 8e9801dfe37c9e68cdbfcd15988df2187191864e
2.ocfs2: o2net: don't shutdown connection when idle timeout
 c43c363def04cdaed0d9e26dae846081f55714e7

They are works well as we shut down and up the Ethernet interface manually and 
intervals to create the scenarios with shell scripts, the issues cat not be 
recreated.
Thanks you for reviews and better advices.

There is another question.
As the node number rises to 32 or 128 in one cluster, we think the TCP keep 
alive MSG interval should be make longer from 2 seconds to 10 seconds and the 
idle timeout value should be 6ms or 9ms.
We think it can reduce the non-useful keep alive messages and improve the 
performance of the TCP connection.
O2CB_IDLE_TIMEOUT_MS=3  to  9
O2CB_KEEPALIVE_DELAY_MS=2000  to  1

We test the values and the changes works well.
Is there any side effect? We are forward your better thoughts about that.
Thanks.

-
本邮件及其附件含有杭州华三通信技术有限公司的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!
___
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

Re: [Ocfs2-devel] Ocfs2-devel Digest, Vol 127, Issue 25

2014-10-09 Thread Joseph Qi
On 2014/10/9 15:16, Guozhonghua wrote:
 Hi Joseph and Srinivas,
 
 We had merged and test the two patches:
 1.ocfs2: o2net: set tcp user timeout to max value
  8e9801dfe37c9e68cdbfcd15988df2187191864e
 2.ocfs2: o2net: don't shutdown connection when idle timeout
  c43c363def04cdaed0d9e26dae846081f55714e7
 
 They are works well as we shut down and up the Ethernet interface manually 
 and intervals to create the scenarios with shell scripts, the issues cat not 
 be recreated.
 Thanks you for reviews and better advices.
 
 There is another question.
 As the node number rises to 32 or 128 in one cluster, we think the TCP keep 
 alive MSG interval should be make longer from 2 seconds to 10 seconds and the 
 idle timeout value should be 6ms or 9ms.
 We think it can reduce the non-useful keep alive messages and improve the 
 performance of the TCP connection.
 O2CB_IDLE_TIMEOUT_MS=3  to  9
 O2CB_KEEPALIVE_DELAY_MS=2000  to  1
 
In my opinion, O2CB_IDLE_TIMEOUT_MS can be changed to suit your scenario.
But for O2CB_KEEPALIVE_DELAY_MS, I don't think you have to change it.
It will send keepalive packet only if there is no DLM messages between nodes.

 We test the values and the changes works well.
 Is there any side effect? We are forward your better thoughts about that.
 Thanks.
 
 -
 本邮件及其附件含有杭州华三通信技术有限公司的保密信息,仅限于发送给上面地址中列出
 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
 邮件!
 This e-mail and its attachments contain confidential information from H3C, 
 which is
 intended only for the person or entity whose address is listed above. Any use 
 of the
 information contained herein in any way (including, but not limited to, total 
 or partial
 disclosure, reproduction, or dissemination) by persons other than the intended
 recipient(s) is prohibited. If you receive this e-mail in error, please 
 notify the sender
 by phone or email immediately and delete it!
 


___
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

[Ocfs2-devel] Hi, is there any way to restore the corrupted disk? Thanks.

2014-10-09 Thread Guozhonghua
Hi, All

As we test the OCFS2, the disk is corrupted with dd command manually and so 
some meta data is lost.
We restore the data, there is about 1M meta data can't restored.
How can we restore the data from disk?
So from 0010 to 00207000, the meta data is lost.
Is anywhere on the disk backup this meta data?
Thanks

fsck.ocfs2 -r 6 /dev/sdd
fsck.ocfs2 1.6.3
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup 
block#268435456? n y
fsck.ocfs2: Bad magic number in inode while initializing the DLM

fsck.ocfs2 -fpy /dev/sdd
fsck.ocfs2 1.6.3
fsck.ocfs2: Bad magic number in inode while initializing the DLM


2180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
0020  00 00 00 00 00 40 00 00  00 00 00 00 00 00 00 00  |.@..|
00200010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
00207000  49 4e 4f 44 45 30 31 00  f7 50 ac 08 ff ff 07 00  |INODE01..P..|


The disk layout is as below:
root@H3CRDS14-RD:~# hexdump -C /dev/sdd |more
  02 02 02 02 02 02 02 02  74 68 69 73 20 69 73 20  |this is |
0010  61 6e 20 6f 63 66 73 32  20 76 6f 6c 75 6d 65 00  |an ocfs2 volume.|
0020  02 02 02 02 02 02 02 02  02 02 02 02 02 02 02 02  ||
*
0080  02 02 02 02 02 02 02 02  74 68 69 73 20 69 73 20  |this is |
0090  61 6e 20 6f 63 66 73 32  20 76 6f 6c 75 6d 65 00  |an ocfs2 volume.|
00a0  02 02 02 02 02 02 02 02  02 02 02 02 02 02 02 02  ||
*
0230  74 68 69 73 20 69 73 20  61 6e 20 6f 63 66 73 32  |this is an ocfs2|
0240  20 76 6f 6c 75 6d 65 00  02 02 02 02 02 02 02 02  | volume.|
0250  02 02 02 02 02 02 02 02  02 02 02 02 02 02 02 02  ||
*
0280  02 02 02 02 74 68 69 73  20 69 73 20 61 6e 20 6f  |this is an o|
0290  63 66 73 32 20 76 6f 6c  75 6d 65 00 02 02 02 02  |cfs2 volume.|
02a0  02 02 02 02 02 02 02 02  02 02 02 02 02 02 02 02  ||
*
2000  4f 43 46 53 56 32 00 00  f7 50 ac 08 ff ff ff ff  |OCFSV2...P..|
2010  00 00 00 00 00 00 30 00  00 00 00 00 00 00 00 00  |..0.|
2020  00 00 00 00 00 00 00 00  00 00 00 00 31 00 00 00  |1...|
2030  00 00 00 00 00 00 00 00  ad 60 38 51 00 00 00 00  |.`8Q|
2040  ad 60 38 51 00 00 00 00  00 00 00 00 00 00 00 00  |.`8Q|
2050  02 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
2060  f7 50 ac 08 00 00 00 00  00 00 00 00 00 00 00 00  |.P..|
2070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
20c0  00 00 5a 00 00 00 14 00  00 00 00 00 00 00 00 00  |..Z.|
20d0  ad 60 38 51 00 00 00 00  00 00 00 00 03 00 00 00  |.`8Q|
20e0  50 12 00 00 01 00 00 00  01 02 00 00 00 00 00 00  |P...|
20f0  02 02 00 00 00 00 00 00  0c 00 00 00 14 00 00 00  ||
2100  20 00 00 00 9e 53 a1 c8  00 01 00 00 00 00 00 00  | S..|
2110  74 61 72 67 65 74 31 30  31 00 00 00 00 00 00 00  |target101...|
2120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
2150  03 5b a0 58 db fc 4e a7  81 c1 31 4a f5 ae 3c a3  |.[.X..N...1J...|
2160  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
2170  00 00 00 00 00 00 00 00  00 01 00 00 00 00 00 00  ||
2180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
0020  00 00 00 00 00 40 00 00  00 00 00 00 00 00 00 00  |.@..|
00200010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
00207000  49 4e 4f 44 45 30 31 00  f7 50 ac 08 ff ff 07 00  |INODE01..P..|
00207010  00 00 00 00 00 00 30 00  00 00 00 00 00 00 00 00  |..0.|
00207020  00 00 00 00 00 03 00 00  a4 81 01 00 91 04 00 00  ||
00207030  ad 60 38 51 00 00 00 00  ad 60 38 51 00 00 00 00  |.`8Q.`8Q|
00207040  ad 60 38 51 00 00 00 00  00 00 00 00 00 00 00 00  |.`8Q|
00207050  07 02 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
00207060  f7 50 ac 08 00 00 00 00  00 00 00 00 00 00 00 00  |.P..|
00207070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
-
本邮件及其附件含有杭州华三通信技术有限公司的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email 

Re: [Ocfs2-devel] Ocfs2-devel Digest, Vol 127, Issue 25

2014-10-09 Thread Srinivas Eeda
On 10/09/2014 12:53 AM, Joseph Qi wrote:
 On 2014/10/9 15:16, Guozhonghua wrote:
 Hi Joseph and Srinivas,

 We had merged and test the two patches:
 1.ocfs2: o2net: set tcp user timeout to max value
   8e9801dfe37c9e68cdbfcd15988df2187191864e
 2.ocfs2: o2net: don't shutdown connection when idle timeout
   c43c363def04cdaed0d9e26dae846081f55714e7

 They are works well as we shut down and up the Ethernet interface manually 
 and intervals to create the scenarios with shell scripts, the issues cat not 
 be recreated.
 Thanks you for reviews and better advices.

 There is another question.
 As the node number rises to 32 or 128 in one cluster, we think the TCP keep 
 alive MSG interval should be make longer from 2 seconds to 10 seconds and 
 the idle timeout value should be 6ms or 9ms.
 We think it can reduce the non-useful keep alive messages and improve the 
 performance of the TCP connection.
 O2CB_IDLE_TIMEOUT_MS=3  to  9
 O2CB_KEEPALIVE_DELAY_MS=2000  to  1

 In my opinion, O2CB_IDLE_TIMEOUT_MS can be changed to suit your scenario.
 But for O2CB_KEEPALIVE_DELAY_MS, I don't think you have to change it.
 It will send keepalive packet only if there is no DLM messages between nodes.

 We test the values and the changes works well.
As Joseph explained they both are tunables, you can run service o2cb 
configure to change values. It falls down to how sensitive your 
application want to be to detect network problems.

Can you please elaborate on what you meant by changes works well. How 
did you test it and what you found ?

 Is there any side effect? We are forward your better thoughts about that.
 Thanks.

 -
 本邮件及其附件含有杭州华三通信技术有限公司的保密信息,仅限于发送给上面地址中列出
 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
 邮件!
 This e-mail and its attachments contain confidential information from H3C, 
 which is
 intended only for the person or entity whose address is listed above. Any 
 use of the
 information contained herein in any way (including, but not limited to, 
 total or partial
 disclosure, reproduction, or dissemination) by persons other than the 
 intended
 recipient(s) is prohibited. If you receive this e-mail in error, please 
 notify the sender
 by phone or email immediately and delete it!



___
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel