[ovs-dev] [PATCH branch-1.4] ovsdb: Allow recovery from transient write errors in log implementation.

[Ben Pfaff]

On Fri, May 03, 2013 at 06:53:28PM +0100, Zoltan Kiss wrote:
> Until now, the OVSDB data journaling implementation has made write errors
> "sticky", so that a single write error persists as long as ovsdb-server is
> alive.  However, some kinds of write errors (such as ENOSPC) can be
> transient in practice.  I don't know of a good reason to make such errors
> sticky, so this commit makes the journaling code retry writes even after
> an error occurs, allowing ovsdb-server to recover from transient errors.
> 
> This is a crossport of commit a7bf837f065d81fbc0dab0a372a7b756094a5322
> from master.
> 
> Reported-by: likunyun <kunyunli at hotmail.com>
> Signed-off-by: Ben Pfaff <blp at nicira.com>
> Acked-by: Ethan Jackson <ethan at nicira.com>
> Backported-by: Zoltan Kiss <zoltan.kiss at citrix.com>
> Signed-off-by: Zoltan Kiss <zoltan.kiss at citrix.com>

I cherry-picked the original commit to branch-1.4 and branch-1.9.