Re: corruption issue after server crash - ERROR: unexpected chunk number 0

On Thu, Nov 21, 2013 at 4:14 PM, John R Pierce <pierce@hogranch.com> wrote:
> On 11/21/2013 2:51 PM, Kevin Grittner wrote:
>>
>> That leaves three possibilities:
>>    (1)  fsync doesn't actually guarantee persistence in your stack.
>
>
> I'll put my $5 on (1).... virtualization stacks add way too much ooga-booga
> to the storage stack, and tend to play fast and loose with write buffering
> to maintain some semblence of performance.

If you really hate your database, be sure and include an NFS mount at
the vm image level in there somewhere.