I'm no expert but if I was in the same situation, I would definately keep the
integrity check on. Especially since your only running a raid5, the sooner you
know there is a problem the better. Even if zfs can not fix it for you it can
still be a useful tool. Basically a few errors may not be worth fixing
manually, but if lots of errors start happening, your better off knowing before
a full drive failure. Now in certain situations, the extra overhead may not be
worth the extra relyability. But that's a much more complex discussion, that
would need a lot more information.
------Original Message------
From: Espen Martinsen
Sender: zfs-discuss-boun...@opensolaris.org
To: zfs Discuss
Subject: [zfs-discuss] Zpool without any redundancy
Sent: Oct 20, 2009 12:49 AM
Hi,
This might be a stupid question, but I can't figure it out.
Let's say I've chosen to live with a zpool without redundancy,
(SAN disks, has actually raid5 in disk-cabinet)
m...@mybox:~# zpool status BACKUP
pool: BACKUP
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
BACKUP ONLINE 0 0 0
c0t200400A0B829BC13d0 ONLINE 0 0 0
c0t200400A0B829BC13d1 ONLINE 0 0 0
c0t200400A0B829BC13d2 ONLINE 0 0 0
errors: No known data errors
The question:
Would it be a good idea to torn OFF the 'checksum' property of the ZFS
filesystems?
I know the manual says it is not recommended to turn off integrity of
user-data, but what
will happen if the algorithm actually finds one? I would not have any way to
fix that, except
delete/overrite the data. (will I be able to point out what files are involved)
Yours
Espen Martinsen
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Sent from my BlackBerry® smartphone with SprintSpeed
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
