As we known, truncate is just a special case of punching holes(from new i_size
to end), we therefore could take advantage of existing
ocfs2_remove_btree_range()
codes to reduce the comlexity and redundancy in alloc.c, the goal here is to
make
truncate codes more generic and straightforward.
Sunil,
On 10-01-27 12:09, Sunil Mushran wrote:
Wengang Wang wrote:
I think the timer is not a very good idea. Canceling an ocfs2 cluster
lock is not complex though it needs lines of code changes. By your
word, I felt you are meaning that the timer is a separated thing
from
Wengang Wang wrote:
cancel convert for what? only the freeze lock or a command interface for
all cluster lock?
I don't know if it's needed for a commond cluster lock. But anyway,
seems the freeze/thaw relies on a cancelable(or a timeout version of) cluster
lock. Otherwise, the lock will wait
David Teigland wrote:
Oops, yeah, I missed copying that:
Jan 26 10:08:31 bull-02 kernel: (1995,1):ocfs2_prepare_downconvert:3280
ERROR: lockres-l_level (0) = new_level (0)
Jan 26 10:08:31 bull-02 kernel: [ cut here ]
Jan 26 10:08:31 bull-02 kernel: kernel BUG at
When a ocfs2 network heartbeat times out between two nodes, o2net layer breaks
the socket connection, and returns -ENOTCONN to processes that are trying
send/receive messages to/from other node. It also queues a quorum decision to
be made after the disk timeout to resolve split brain.
The fix
This patch rollbacks earlier fix that tries to re-establish network connection
when network timeout happens. Reconnect was re-cycling sockets which results
in lost messages resulting in hangs.
Signed-off-by: Srinivas Eeda srinivas.e...@oracle.com
---
fs/ocfs2/cluster/tcp.c | 50
Following 3 patches fixes:
1. rollback's reconnect fix
2. delay enotconn for sends, receives till a node reconnects/dies after a
lost connection.
3. Correct's keepalive protocol
Thanks,
--Srini
___
Ocfs2-devel mailing list
