From owner-freebsd-questions@FreeBSD.ORG Mon Nov 8 20:02:04 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CE95106566C for ; Mon, 8 Nov 2010 20:02:04 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with ESMTP id A17598FC33 for ; Mon, 8 Nov 2010 20:02:03 +0000 (UTC) Received: from [127.0.0.1] (unknown [192.168.4.11]) (Authenticated sender: svein-listmail) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id CDA0822; Mon, 8 Nov 2010 21:02:02 +0100 (CET) Message-ID: <4CD85736.1000207@stillbilde.net> Date: Mon, 08 Nov 2010 21:01:58 +0100 From: "Svein Skogen (Listmail account)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5 MIME-Version: 1.0 To: Arthur Chance References: <20101106203016.GB13095@guilt.hydra> <20101106213836.GA77198@slackbox.erewhon.net> <4CD8194D.7080208@qeng-ho.org> <4CD82081.50309@stillbilde.net> <4CD837C9.6090800@qeng-ho.org> In-Reply-To: <4CD837C9.6090800@qeng-ho.org> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4DAEEF70CA1A44E265BC4861" Cc: freebsd-questions@freebsd.org Subject: Re: ZFS License and Future X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2010 20:02:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4DAEEF70CA1A44E265BC4861 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 08.11.2010 18:47, Arthur Chance wrote: *snip* >=20 > Presuming you're talking about ZFS, the hash isn't intended to correct > hardware errors, it's only there to detect them. Correction comes from > mirroring or the use of RAIDZ{1,2,3}. (I have personal experience of ho= w > well that works, as I had a disk in a RAIDZ array go bad suddenly, and = I > didn't lose any data.) Any new solution would almost certainly mimic > ZFS's approach of arranging the data as a Merkel tree, and using > multiple copies or N out of M shares for correction. I'm not sure GEOM'= s > block orientation fits well with Merkel trees though, although I'd be > happy to be corrected by a GEOM expert. No, I'm talking about knowing that a file has been corrupted is a little better than not knowing it has been corrupted. But it still won't help bring back the file. And I'm ... all too familiar with redundancy strategies (and backups). Including their shortcomings. Speaking of which: Has there been any progress on properly backing up ZFS on FreeBSD yet? (including the metada= ta) //Svein --=20 --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg =D8stli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE --------+-------------------+------------------------------- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ ------------------------------------------------------------ --------------enig4DAEEF70CA1A44E265BC4861 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzYVzoACgkQODUnwSLUlKTacgCfXpsbvPBqXlaqp/XwCgAA+CpF 0aoAoJuwyLyehHLEylZ1eycv85Y9G2US =Z59d -----END PGP SIGNATURE----- --------------enig4DAEEF70CA1A44E265BC4861--