Just to close out the discussion, I wasn't able to prove any issues with
ZFS. The files that were changed all seem to have plausible scenarios.
I've moved my external USB drive backups over to ZFS directly connected
to the file server and it's all working fine.
Thanks for everyone's help!
-
On Oct 24, 2011, at 9:42, Edward Ned Harvey
wrote:
>
> I would suggest finding a way to connect the external disks directly to the
> ZFS server, and start using zfs send instead.
>
Since these were my offsite backups I was using Truecrypt which drove the use
of ext3 and Linux. Also I wanted
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Robert Watzlavick
>
> I have two external USB hard drives
> that I use to back up the contents of the ZFS raidz on alternating
> months. The USB hard drives use EXT3 so they are connected to a
On Sat, Oct 22, 2011 at 12:27 PM, Robert Watzlavick
wrote:
> 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" version from the web.
I ran into a similar "failure" with a
> From: Robert Watzlavick [mailto:rob...@watzlavick.com]
> Sent: Sunday, October 23, 2011 4:36 PM
>
> Now on to find out why the 3 Acronis Backup files got modified. This is
> good news so far...
I expect you'll find the same thing for Acronis. Acronis updates those
individual files to make the
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
On Oct 22, 2011, at 9:27 AM, Robert Watzlavick wrote:
> I've noticed something strange over the past few months with four files on my
On 10/22/2011 04:14 PM, Mark Sandrock wrote:
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
I found something interesting with the .ppt file. Apparently, just
opening a .ppt
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
12 matches
Mail list logo
