Now this is a testament to the power of ZFS. Only ZFS is so sensitive it
observed these errors to you. Had you run another filesystem, you would never
got a notice that your data is slowly being corrupted by some faulty hardware.
:o)
--
This message posted from opensolaris.org
Just following up...
I reran memtest diagnostics and let it run overnight again. This time I did
see some memory errors - which would be the most likely explanation for the
errors I am seeing.
Faulty hardware strikes again.
Thanks to all for the advice.
Warren
> Comments below...
>
>
Comments below...
On Sep 12, 2010, at 2:56 PM, Warren Strange wrote:
>> So we are clear, you are running VirtualBox on ZFS,
>> rather than ZFS on VirtualBox?
>>
>
> Correct
>
>>
>> Bad power supply, HBA, cables, or other common cause.
>> To help you determine the sort of corruption, for
>> mir
> So we are clear, you are running VirtualBox on ZFS,
> rather than ZFS on VirtualBox?
>
Correct
>
> Bad power supply, HBA, cables, or other common cause.
> To help you determine the sort of corruption, for
> mirrored pools FMA will record
> the nature of the discrepancies.
> fmdump -eV
On Sep 12, 2010, at 11:05 AM, Warren Strange wrote:
> I posted the following to the VirtualBox forum. I would be interested in
> finding out if anyone else has ever seen zpool corruption with VirtualBox as
> a host on OpenSolaris:
>
> -
> I am running Ope
Hi Warren,
This may not help much, except perhaps as a way to eliminate possible
causes, but I ran b134 with VirtualBox and guests on ZFS for quite a
long time without any such symptoms. My pool is a simple, unmirrored
one, so the difference may be there. I used shared folders without
inciden
