Why don't you see which byte differs, and how it does?
Maybe that would suggest the "failure mode". Is it the
same byte data in all affected files, for instance?
Mark
Sent from my iPhone
On Oct 22, 2011, at 2:08 PM, Robert Watzlavick wrote:
> On Oct 22, 2011, at 13:14, Edward Ned Harvey
> wr
On Oct 22, 2011, at 12:55, Garrett D'Amore wrote:
> You're using an *old* version of both OpenSolaris and zpool. There have been
> a few corruption bugs fixed since then. I'd recommend updating.
>
>- Garrett
>
I was looking for the changelist to see if any have been fixed but couldnt fi
On Oct 22, 2011, at 13:14, Edward Ned Harvey
wrote:
>>
> How can you outrule the possibility of "something changed the file."
> Intentionally, not as a form of filesystem corruption.
I suppose that's possible but seems unlikely. One byte on a file changed on the
disk with no corresponding chan
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Robert Watzlavick
>
> What failure scenario could have caused this? The file was obviously
> initially good on the raidz because it got backed up to the USB drive
> and that matches the "good
I've noticed something strange over the past few months with four files
on my raidz. Here's the setup:
OpenSolaris snv_111b
ZFS Pool version 14
AMD-based server with ECC RAM.
5 ST3500630AS 500 GB SATA drives (4 active plus spare) in raidz1
The other day, I observed what appears to be undetected
On Sat, Oct 22, 2011 at 11:36 AM, Paul Kraus wrote:
> Recently someone posted to this list of that _exact_ situation, they loaded
> an OS to a pair of drives while a pair of different drives containing an OS
> were still attached. The zpool on the first pair ended up not being able to
> be importe
