Xavi Hernandez

/run regression

> > What's the benefit of this approach compared to creating a temporary file and then renaming it ? > > The issue was due to truncation of the contents...

Could you try to disable `open-behind`, `quick-read`, `stat-prefetch` and `io-cache` (this one should already be disabled by default, though) ? # gluster volume set <volname&gt> open-behind off # gluster volume...

You can also disable `read-ahead` if enabled.

> Apologies for the delayed response, I got sidetracked. Anyway, I can confirm that using the Gluster options mentioned above (`open-behind`, `quick-read`, `stat-prefetch`, `io-cache`, and `read-ahead` all `off`) along with...

@jkroonza does your workload contain a lot of renames ? Is your volume configuration stable, or do you change some setting frequently (at least once between crashes) ? Do you...

And one more thing: do you get crashes in bricks and clients, or only on clients ? If both crash, is the frequency similar ?

It would be interesting to analyze a core dump after the latest change, but I'm not sure how to do that on Gentoo. Is it easy to setup an environment...

> > @jkroonza - I assume this is without cherry-picking #3226 which I remember you've looked at? IOW, just the hash changes? > > Correct. Cherry-picking #3226 is non trivial....

/recheck smoke