Yes, confirmed. Every site that reported this issue reported it resolved with this patch. Andreas Dilger wrote: > <snip> > The patch shows in bugzilla as landed-1.8.3, and the 1.8.3 ChangeLog also lists a fix for bug 22177, so I'd say it is fixed. > > >