In a raid1 situation, it will also rewrite the effected data, on the
drive that failed the checksum
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson:
In a raid1 situation, it will also rewrite the effected data, on the
drive that failed the checksum
Will it do so without an explicit scrub?
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B
On Sun, Oct 28, 2012 at 02:23:51PM +0100, Martin Steigerwald wrote:
Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson:
In a raid1 situation, it will also rewrite the effected data, on the
drive that failed the checksum
Will it do so without an explicit scrub?
If a failed checksum
Am Sonntag, 28. Oktober 2012 schrieb Hugo Mills:
On Sun, Oct 28, 2012 at 02:23:51PM +0100, Martin Steigerwald wrote:
Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson:
In a raid1 situation, it will also rewrite the effected data, on
the drive that failed the checksum
Will it do
On Sun, Oct 28, 2012 at 02:36:24PM +0100, Martin Steigerwald wrote:
Am Sonntag, 28. Oktober 2012 schrieb Hugo Mills:
On Sun, Oct 28, 2012 at 02:23:51PM +0100, Martin Steigerwald wrote:
Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson:
In a raid1 situation, it will also rewrite the
On Sat, Oct 27, 2012 at 09:56:45PM +, Michael Kjörling wrote:
I came across the tidbit that ZFS has a contract guarantee that the
data read back will either be correct (the checksum computed over the
data read from the disk matches the checksum stored on disk), or you
get an I/O error.
On 27 Oct 2012 23:02 +0100, from h...@carfax.org.uk (Hugo Mills):
I came across the tidbit that ZFS has a contract guarantee that the
data read back will either be correct (the checksum computed over the
data read from the disk matches the checksum stored on disk), or you
get an I/O error.
