c> 2. if the .vmdk's were stored in ZFS why was the corruption not
c> flagged as a CKSUM error?
wm> They were. From the OP:
>NAMESTATE READ WRITE CKSUM
>testing ONLINE 0 016
> mirrorONLINE 0 0
On Thu, Sep 25, 2008 at 13:38, Miles Nordin <[EMAIL PROTECTED]> wrote:
> 1. too bad Sil is the only ones selling chips on PCI cards that have
> source code for their drivers.
Indeed, it is too bad. But I'd rather have a working closed blob than
a driver that is Free Software for a device that is
> "np" == Neal Pollack <[EMAIL PROTECTED]> writes:
np> No attempt to acknowledge or recall defective silicon. No
np> interest in customer data loss. Well, this customer has no
np> further interest in Silicon Image. I refuse to acknowledge
np> that they exist.
1. too bad Sil
On 09/24/08 10:57 PM, Jeff Bonwick wrote:
It's almost certainly the SIL3114 controller.
Google "SIL3114 data corruption" -- it's nasty.
I've also in the past had the misfortune of experiencing
Silicon Image. My corruption was with other file types
and not even ZFS. Silicon Image is someth
It's almost certainly the SIL3114 controller.
Google "SIL3114 data corruption" -- it's nasty.
Jeff
On Thu, Sep 25, 2008 at 07:50:01AM +0200, Mikael Karlsson wrote:
> I have a strange problem involving changes in large file on a mirrored
> zpool in
> Open solaris snv96.
> We use it at storage in
I have a strange problem involving changes in large file on a mirrored
zpool in
Open solaris snv96.
We use it at storage in a VMware ESXi lab environment. All virtual disk
files gets
corrupted when changes are made within the files (when running the
machine that is).
The "sad" thing is that I'v
