We're were running 7.0.1.1, build 11, and we suffered this exact problem despite these files being owned by causer:casusers, and the permissions being correct. So while this may be part of a workaround for some, it's not a complete solution and thus ...