ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
* [Ocfs2-devel]  [RFC] ocfs2: Double about ocfs2_trylock_journal
@ 2016-03-01  3:19 jiangyiwen
  0 siblings, 0 replies; only message in thread
From: jiangyiwen @ 2016-03-01  3:19 UTC (permalink / raw)
  To: ocfs2-devel

ocfs2_trylock_journal() is used to test if the node who occupied this
slot is alive in ocfs2_mark_dead_nodes(), but actually it can't achieve
the desired results. The problem can be described as follows:

N1              N2                        N3
crash, previously
occupied in slot 1
                begin mount, only have
                N2,N3 in domain_map,
                and found slot 1 is occupied,
                then call ocfs2_trylock_journal()
                                          N3 is lockres master of
                                          journal:0001, but N3 doesn't
                                          find N1 down, so return
                                          DLM_NOTQUEUED to N2
                Because N3 doesn't find N1
                down, so ocfs2_trylock_journal()
                return EAGAIN, and will not
                recover N1
                                          in this moment, N3 crash
                N2 only recover N3 in this
                situation, and then begin
                update some meta data which
                also have been operated in
                journal:0001
N1 starts, mount
volume, and recover
journal:0001, this
will cover meta data
which N2 has modified,
and then cause filesystem
is destroyed.

So I want to know if someone has a good idea to solve this problem?

Thanks,
Yiwen Jiang.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-03-01  3:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-01  3:19 [Ocfs2-devel] [RFC] ocfs2: Double about ocfs2_trylock_journal jiangyiwen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).