[Bugs] [Bug 1531457] hard Link file A to B error if A is just created

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1531457



--- Comment #1 from George <george.lian at nokia.com> ---
I found a bug fix in 
////////////////////////////////////////////////////
SHA-1: 4c4624c9bad2edf27128cb122c64f15d7d63bbc8

* cluster/afr: Don't let NFS cache stat after writes

Problem:
Afr does post-ops after write but the stat buffer it unwinds is at the
time of write, so if nfs client caches this, it will see different
ctime when it does stat on it after post-op is done. From NFS client's
perspective it thinks the file is changed. Tar which depends on this
to be correct keeps giving 'file changed as we read it' warning.
If Afr instead has to choose to unwind after post-op, eager-lock,
delayed-post-op will have to be disabled which will lead to bad
performance for all write usecases.

Fix:
Don't let client cache stat after write.

Change-Id: Ic6062acc6e5cdd97a9c83c56bd529ec83cee8a23
BUG: 1302948
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
///////////////////////////////////////////////////////////

from my understand, the link issue maybe introduced by the above fix.
in this fix, it set the ia_nlink to in function gf_zero_fill_stat, and it
leadto kernel treat it as the non-exist file with the code script I shared in
issue report.
@Pranith Kumar K, could you please have a check and give your comments?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.