Hi Abhishek,
The files that are reporting i/o error have gfid-mismatch. This situation is
called directory or entry split-brain. You can find steps to resolve this kind
of split brain here :
https://gluster.readthedocs.org/en/latest/Troubleshooting/split-brain/ .
Ideally, the parent
flush-behind default is probably fine as without fsync there is no
guarantee of file contents syncing to disk.
Pranith
On 03/16/2016 04:16 PM, Pranith Kumar Karampuri wrote:
hi Raghavendra,
Krutika showed me this code in write-behind about not honoring
O_DIRECT. 1) Is there any reason
hi Raghavendra,
Krutika showed me this code in write-behind about not honoring
O_DIRECT. 1) Is there any reason why we do flush-behind by default and
2) Not honor O_DIRECT in write-behind by default (strict-O_DIRECT option)?
Pranith
___
