Hi I have two annoying bugs in 3.2.5. I wonder if there is a patch to test, or a change to backport from master in order to address them 1) Adding a brick or rebalancing a volume changes inodes, and therefore wreak processes that were working on files when the operation is done. I was told a few weeks ago that this was known and it would be adressed. Any update 2) When using AFR, if a peer goes down, processes that have I/O pending will se an error. Just retrying the same operation is fine, but that is a bit furstrating. -- Emmanuel Dreyfus manu@xxxxxxxxxx
