On Thu, Aug 18, 2011 at 04:25:55PM +0200, Michal Privoznik wrote:
> On 18.08.2011 15:55, Eric Blake wrote:
> > On 08/18/2011 07:44 AM, Michal Privoznik wrote:
> >> Although we are flushing cache after some critical writes (e.g.
> >> volume creation), after some others we do not (e.g. volume cloning
On 19.08.2011 11:04, Daniel Veillard wrote:
> On Thu, Aug 18, 2011 at 04:25:55PM +0200, Michal Privoznik wrote:
>> On 18.08.2011 15:55, Eric Blake wrote:
>>> On 08/18/2011 07:44 AM, Michal Privoznik wrote:
Although we are flushing cache after some critical writes (e.g.
volume creation), a
On 18.08.2011 15:55, Eric Blake wrote:
> On 08/18/2011 07:44 AM, Michal Privoznik wrote:
>> Although we are flushing cache after some critical writes (e.g.
>> volume creation), after some others we do not (e.g. volume cloning).
>> This patch fix this issue. That is for volume cloning, writing
>> he
On 08/18/2011 07:44 AM, Michal Privoznik wrote:
Although we are flushing cache after some critical writes (e.g.
volume creation), after some others we do not (e.g. volume cloning).
This patch fix this issue. That is for volume cloning, writing
header of logical volume, and storage wipe.
---
src
Although we are flushing cache after some critical writes (e.g.
volume creation), after some others we do not (e.g. volume cloning).
This patch fix this issue. That is for volume cloning, writing
header of logical volume, and storage wipe.
---
src/storage/storage_backend.c |8